Log message:
postgresql: updated to 17.3, 16.7, 15.11, 14.16, 13.19

PostgreSQL 17.3, 16.7, 15.11, 14.16, and 13.19

Security Issues

CVE-2025-1094: PostgreSQL quoting APIs miss neutralizing quoting syntax in text \ 
that fails encoding validation

Bug Fixes and Improvements

This update fixes over 70 bugs that were reported in the last several months. \ 
The issues listed below affect PostgreSQL 17. Some of these issues may also \ 
affect other supported versions of PostgreSQL.

Restore pre-v17 truncation behavior for >63-byte database names and usernames \ 
in connection requests.
Don't perform connection privilege checks and limits on parallel workers, and \ 
instead inherit these from the leader process.
Remove Lock suffix from LWLock wait event names.
Fix possible re-use of stale results in window aggregates, which could lead to \ 
incorrect results.
Several race condition fixes for vacuum that in the worst case could cause \ 
corruption to a system catalog.
Several fixes for truncating tables and indexes that prevent potential corruption.
Fix for detaching a partition where its own foreign-key constraint references a \ 
partitioned table.
Fix for the FFn (e.g., FF1) format codes for to_timestamp, where an integer \ 
format code before the FFn would consume all available digits.
Fixes for SQL/JSON and XMLTABLE() to double-quote specific entries when necessary.
Include the ldapscheme option in pg_hba_file_rules().
Several fixes for UNION, including not merging columns with non-compatible \ 
collations.
Several fixes that could impact availability or speed of starting a connection \ 
to PostgreSQL.
Fix multiple memory leaks in logical decoding output.
Fix several memory leaks in PL/Python.
Add psql tab completion for COPY (MERGE INTO).
Make pg_controldata more resilient when displaying info from corruptedpg_control \ 
files.
Fix for a memory leak in pg_restore with zstd-compressed data.
Fix pg_basebackup to correctly handle pg_wal.tar files exceeding 2GB on Windows.
Modify earthdistance to use SQL-standard function bodies, which fixes possible \ 
issues with major version upgrades to v17 when databases use this extension.
Fix crash in pageinspect in instances where the brin_page_items() function \ 
definition is not updated to the latest version.
Fix race condition when trying to cancel a postgres_fdw remote query.

Log message:
postgresql: updated to 17.1, 16.5, 15.9, 14.14, 13.17

PostgreSQL 12 is now end-of-life.

Security Issues
* CVE-2024-10976: PostgreSQL row security below e.g. subqueries disregards user \ 
ID changes
* CVE-2024-10977: PostgreSQL libpq retains an error message from man-in-the-middle
* CVE-2024-10978: PostgreSQL SET ROLE, SET SESSION AUTHORIZATION reset to wrong \ 
user ID
* CVE-2024-10979: PostgreSQL PL/Perl environment variable changes execute \ 
arbitrary code

Bug Fixes and Improvements

This update fixes over 35 bugs that were reported in the last several months. \ 
The issues listed below affect PostgreSQL 17. Some of these issues may also \ 
affect other supported versions of PostgreSQL.

Fix when attaching or detaching table partitions with foreign key constraints. \ 
After upgrade, users impacted by this issue will need to perform manual steps to \ 
finish fixing it. Please see the "Upgrading" section and the release \ 
notes for more information.
Fix when using libc as the default collation provider when LC_CTYPE is C while \ 
LC_COLLATE is a different locale. This could lead to incorrect query results. If \ 
you have these settings in your database, please reindex any affected indexes \ 
after updating to this release. This issue impacted 17.0 only.
Several query planner fixes, including disallowing joining partitions \ 
(partitionwise join) if the collations of the partitions don't match.
Fix possible wrong answers or wrong varnullingrels planner errors for MERGE ... \ 
WHEN NOT MATCHED BY SOURCE actions.
Fix validation of the COPY FORCE_NOT_NULL and FORCE_NULL.
Fix server crash when a json_objectagg() call contains a volatile function.
Ensure there's a registered dependency between a partitioned table and a \ 
non-built-in access method specified in CREATE TABLE ... USING. This fix only \ 
prevents problems for partitioned tables created after this update.
Fix race condition in committing a serializable transaction.
Fix race condition in COMMIT PREPARED that could require manual file removal \ 
after a crash-and-recovery.
Fix for pg_cursors view to prevent errors by excluding cursors that aren't \ 
completely set up.
Reduce logical decoding memory consumption.
Fix to prevent stable functions from receiving stale row values when they're \ 
called from a CALL statement's argument list and the CALL is within a PL/pgSQL \ 
EXCEPTION block.
Fix for JIT crashes on ARM (aarch64) systems.
The psql \watch now treats values that are less than 1ms to be 0 (no wait \ 
between executions).
Fix failure to use credentials for a replication user in the password file (pgpass)
pg_combinebackup now throws an error if an incremental backup file is present in \ 
a directory that should contain a full backup.
Fix to avoid reindexing temporary tables and indexes in vacuumdb and parallel \ 
reindexdb

Log message:
*: recursive bump for icu 76 shlib major version bump

Log message:
Add MAKE_JOBS_SAFE=no

MAKE_JOBS=22 reliably fails for me, so include the following comment

# MAKE_JOBS=22 failed with:
+# In file included from ../../src/include/postgres.h:46, from chklocale.c:17:
+# ../../src/include/utils/elog.h:79:10: fatal error: utils/errcodes.h: No such \ 
file or directory

Log message:
postgresql17: added version 17.0

PostgreSQL 17 builds on decades of open source development, improving its
performance and scalability while adapting to emergent data access and storage
patterns. This release of PostgreSQL adds significant overall performance
gains, including an overhauled memory management implementation for vacuum,
optimizations to storage access and improvements for high concurrency
workloads, speedups in bulk loading and exports, and query execution
improvements for indexes. PostgreSQL 17 has features that benefit brand new
workloads and critical systems alike, such as additions to the developer
experience with the SQL/JSON JSON_TABLE command, and enhancements to logical
replication that simplify management of high availability workloads and major
version upgrades.