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)
bhyve/riscv: fix PCIe FDT interrupt-map entry stride
In bhyve arm64, each PCIe interrupt-map entry spans 10 cells because the
ARM GIC specifies #interrupt-cells = 3. On RISC-V, the APLIC uses
#interrupt-cells = 2, so each entry spans only 9 cells.
When the PCIe FDT code was originally adapted from arm64, the property
allocation size and cell assignments were reduced to 9 cells per entry,
but the loop multiplier retained the 10-cell stride. This caused the
interrupt-map array to be packed incorrectly with gaps, breaking PCI
interrupt routing in guest operating systems and overflowing the
allocation by 16 cells.
Correct the loop stride to 9 cells so the interrupt map is properly
formed.
Reviewed by: jrtc27
Fixes: 7ab1a32cd43c ("bhyve/riscv: Initial import")
MFC after: 3 days
[3 lines not shown]
Revert "bhyve/riscv: fix PCIe FDT interrupt-map entry stride"
Thanks to past me's foolish choice not to alter the commit message such
that none of its lines start with a #, Git got very confused the
cherry-pick and included its own commented-out instructions. Reverting
to re-land with a fixed body.
This is a direct commit to stable/15.
This reverts commit 69f76efd01a72fe0d6cb68442d2c15d3174a268f.
bhyve/riscv: fix PCIe FDT interrupt-map entry stride
In bhyve arm64, each PCIe interrupt-map entry spans 10 cells because the
ARM GIC specifies #interrupt-cells = 3. On RISC-V, the APLIC uses
#interrupt-cells = 2, so each entry spans only 9 cells.
When the PCIe FDT code was originally adapted from arm64, the property
allocation size and cell assignments were reduced to 9 cells per entry,
but the loop multiplier retained the 10-cell stride. This caused the
interrupt-map array to be packed incorrectly with gaps, breaking PCI
interrupt routing in guest operating systems and overflowing the
allocation by 16 cells.
Correct the loop stride to 9 cells so the interrupt map is properly
formed.
Reviewed by: jrtc27
Fixes: 7ab1a32cd43c ("bhyve/riscv: Initial import")
MFC after: 3 days
[25 lines not shown]
style.9: Avoid C++ keywords
Headers may be included by C++ code, and sometimes we might like to
use exinst code as C++. Encourage authors to avoid C++ keywords as
identifiers.
Reviewed by: des, imp (earlier version)
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D61767
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
ipfw: fix off-by-one in the IP_FW_XADD rule count check
Restore the pre-4a77657cbc0 ">=" comparison, otherwise parse_rules_v1()
writes one rule_check_info beyond the allocated buffer.
Do the same in ip_fw_compat.c, which has a copy of the loop but is not
built at the moment.
stable/14 is not affected.
Reviewed by: ae
Fixes: 4a77657cbc0 ("ipfw: migrate ipfw to 32-bit size rule numbers")
MFC after: 1 week
MFC to: stable/15
Found with: Claude Code Opus 5.5
Differential Revision: https://reviews.freebsd.org/D61727
bhyve.8: mention VM nodes in /dev/vmm
Currently, VM nodes in /dev/vmm are only described in the
EXAMPLES section of bhyvectl.8. Add a FILES section to bhyve.8
to make this information easier to find.
Update the bhyvectl.8 example to say "Existing VMs"
instead of "Running VMs" as the VMs listed in /dev/vmm
are not necessarily running.
Update bhyvectl.8 to refer to vmm(4).
Reviewed by: ziaee
MFC after: 3 days
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D61623
tests/sys/pmc: Skip pmc_ss and getmsr_refusals without a hardware PMC
In a guest without a PMU, hwpmc(4) registers only the SOFT class, but
the "instructions" alias still resolves from the pmu-events tables, so
pmc_allocate() fails with EINVAL. pmc_ss_test checked only the alias
and getmsr_refusals required the allocation, so both failed in CI
instead of skipping.
Probe the allocation the tests make and skip if it fails, as
rdpmc_reads_own_counter already does.
PR: 300856 (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=300856)
Reported by: ngie
Reviewed by: mhorne, ngie
Fixes: d546356523f3 ("tests/sys/pmc: add PERF, RDPMC, row, sampling and unload tests")
Sponsored by: Advanced Micro Devices, Inc.
Signed-off-by: Osvaldo Janeri Filho <ojanerif at amd.com>
Differential Revision: https://reviews.freebsd.org/D61689
hwpmc: keep AMD UMC counters from saturating
UMC counters saturate at 2^48 instead of wrapping, after about a day
and a half of memory clock cycles. Clear bit 47 on a read once it is
set and count the carries in the per-CPU overflow count of the PMC,
like the arm64 and armv7 drivers do for their 32-bit counters.
Reviewed by: mhorne
Sponsored by: Advanced Micro Devices, Inc.
Signed-off-by: Osvaldo Janeri Filho <ojanerif at amd.com>
Differential Revision: https://reviews.freebsd.org/D60771