databases/postgresql19-*: Update to 19.0
First production release of the 19 series.
This release introduces the REPACK (CONCURRENTLY) command so users can
optimize tables for their current workload without disruption to ongoing
operations. PostgreSQL 19 gives users better control over plan stability
and query performance with the new pg_plan_advice extension. Developers
will find many delightful features in this release, from support for
"read-your-writes" consistency on standbys to "get or create" behavior
that saves a network round trip.
Upgrading from 18 or earlier requires a dump/restore or pg_upgrade.
Release notes: https://www.postgresql.org/docs/19/release-19.html
(cherry picked from commit 5fa58ac8856ff5bbf8d6b65a0769cdba11e336ed)
databases/postgresql1[45678]-*: Update to latest patch releases
Update to 18.7, 17.12, 16.16, 15.20 and 14.25, fixing 53 CVEs and
a large number of other bugs.
A dump/restore is not required, but some indexes may be corrupt and
should be rebuilt with REINDEX after updating:
- btree indexes on bpchar columns declared without a length
(CHAR(n) is not affected)
- GiST indexes using gist_trgm_ops (contrib/pg_trgm)
- GIN indexes and TOAST-table indexes, if corruption is suspected
For 17 and 18, existing incremental backups should not be trusted.
Take a new full backup after updating and base subsequent
incremental backups on that.
Release notes: https://www.postgresql.org/about/news/postgresql-187-1712-1616-1520-1425-and-19-rc-2-released-3442/
Security: 1a672925-de93-11f1-9824-6cc21735f730
[2 lines not shown]
databases/postgresql19-server: Update to 19RC1
The PostgreSQL Global Development Group announces that the first release
candidate of PostgreSQL 19 is now available for download. As a release
candidate, PostgreSQL 19 RC 1 will be mostly identical to the initial
release of PostgreSQL 19, though some more fixes may be applied prior to
the general availability of PostgreSQL 19.
To upgrade to PostgreSQL 19 RC 1 from earlier versions of PostgreSQL,
you will need to use a major version upgrade strategy, e.g. pg_upgrade
or pg_dump / pg_restore. For more information, please visit the
documentation section on upgrading:
https://www.postgresql.org/about/news/postgresql-19-rc-1-released-3409/
(cherry picked from commit 0ee810cf51b3110956e0ac1076a2ebb6f7de320f)
www/rustfs: Update 1.0.4 to 1.0.5
Stop forcing fat LTO (WITHOUT_LTO), so the build uses the thin LTO from
upstream's release profile.
Make the data directory modifiable with the RUSTFS_DBDIR variable.
Mark BROKEN on i386: rustc runs out of memory.
Changelog: https://github.com/rustfs/rustfs/releases/tag/1.0.5
Reported by: Mickael Maillot <mmaillot at secuserve.com> (memory)
Reported by: pkg-fallout (i386)
Suggested by: otis (RUSTFS_DBDIR)
Reviewed by: otis
Approved by: jrm (mentor)
Differential Revision: https://reviews.freebsd.org/D61470
www/opencloud: Fix build on i386
Fix the build failure on architectures where vendored nats-server's
server/pse package lacks non-cgo FreeBSD implementation (such as i386).
PR: 300899
x11/nvidia-driver{-devel}, x11/nvidia-kmod{-devel}, x11/linux-nvidia-libs{-devel}, graphics/nvidia-drm*-kmod{-devel}, x11/nvidia-settings, x11/nvidia-xconfig: Update to 620.73.04
Update to latest Production Branch of drivers 620.73.04:
https://www.nvidia.com/en-us/drivers/details/285519/
Linux counterparts for x11/linux-nvidia-libs:
https://www.nvidia.com/en-us/drivers/details/285520/
As this version is newer than exisitng New Feature Branch (NFB)
of drivers, update -devel variants to the same version, too.
PR: 300897
Differential Revision: https://reviews.freebsd.org/D61744