Log message:
postgresql1*: updated to 17.2, 16.6, 15.10, 14.15, 13.18, 12.22

PostgreSQL 17.2, 16.6, 15.10, 14.15, 13.18, and 12.22

The issues listed below affect PostgreSQL 17. Some of these issues may also \ 
affect other supported versions of PostgreSQL.

Restore functionality of ALTER ROLE .. SET ROLE and ALTER DATABASE .. SET ROLE. \ 
The fix for CVE-2024-10978 accidentally caused settings for role to not be \ 
applied if they came from non-interactive sources, including previous ALTER \ 
{ROLE|DATABASE} commands and the PGOPTIONS environment variable.
Restore compatibility for the timescaledb and other PostgreSQL extensions built \ 
using PostgreSQL prior to the 2024-11-14 release (17.0, 16.4, 15.8, 14.13, \ 
13.16, 12.20, and earlier). This fix restores struct ResultRelInfo to its \ 
previous size, so that affected extensions don't need to be rebuilt.
Fix cases where a logical replication slot's restart_lsn could go backwards.
Avoid deleting still-needed WAL files during pg_rewind.
Fix race conditions associated with dropping shared statistics entries, which \ 
could lead to loss of statistics data.
Fix crash with ALTER TABLE when checking to see if an index's opclass options \ 
have changed if the table has an index with a non-default operator class.

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:
*: revbump for icu downgrade

Log message:
*: recursive bump for icu 76.1 shlib bump

Log message:
postgresql: updated to 16.4, 15.8, 14.13, 13.16, 12.20

CVE-2024-7348: PostgreSQL relation replacement during pg_dump executes arbitrary SQL

CVSS v3.1 Base Score: 8.8

Supported, Vulnerable Versions: 12 - 16.

An attacker able to create and drop non-temporary objects could inject SQL code \ 
that would be executed by a concurrent pg_dump session with the privileges of \ 
the role running pg_dump (which is often a superuser). The attack involves \ 
replacing a sequence or similar object with a view or foreign table that will \ 
execute malicious code. To prevent this, introduce a new server parameter \ 
restrict_nonsystem_relation_kind that can disable expansion of non-builtin views \ 
as well as access to foreign tables, and teach pg_dump to set it when available. \ 
Note that the attack is prevented only if both pg_dump and the server it is \ 
dumping from are new enough to have this fix.

Bug Fixes and Improvements

Avoid incorrect results from "Merge Right Anti Join" plans, where if \ 
the inner relation is known to have unique join keys, the merge could misbehave \ 
when there are duplicated join keys in the outer relation.
Prevent infinite loop in VACUUM.
Fix partition pruning setup during ALTER TABLE DETACH ... PARTITION CONCURRENTLY.
Fix behavior of stable functions that are used as an argument to a CALL statement.
pg_sequence_last_value() now returns NULL instead of throwing an error when \ 
called on unlogged sequences on standby servers and on temporary sequences of \ 
other sessions.
Fix parsing of ignored operators in websearch_to_tsquery().
Correctly check updatability of view columns targeted by INSERT ... DEFAULT.
Lock owned sequences during ALTER TABLE ... SET LOGGED|UNLOGGED.
Don't throw an error if a queued AFTER trigger no longer exists.
Fix selection of an arbiter index for INSERT ... ON CONFLICT when the desired \ 
index has expressions or predicates, for example, through an updatable view.
Refuse to modify a temporary table of another session with ALTER TABLE.
Fix handling of extended statistics on expressions in CREATE TABLE ... LIKE \ 
STATISTICS.
Fix failure to recalculate sub-queries generated from MIN() or MAX() aggregates.
Disallow underscores in positional parameters.
Avoid crashing when a JIT-inlined backend function throws an error.
Fix handling of subtransactions of prepared transactions when starting a hot \ 
standby server.
Prevent incorrect initialization of logical replication slots.
Fix memory leak in the logical replication WAL sender when publishing changes to \ 
a partitioned table whose partitions have row types that are physically \ 
different from the table.
Disable creation of stateful TLS session tickets by OpenSSL.
Fix how PL/pgSQL handles integer ranges containing underscores (e.g., FOR i IN \ 
1_001..1_002).
Fix incompatibility between PL/Perl and Perl 5.40.
Several fixes related to recursive PL/Python functions and triggers.
Ensure that pg_restore -l reports dependent table of contents entries correctly.
pg_stat_statements now passes a query ID for utility (non-SELECT/INSERT/UPDATE) \ 
statements that appears in SQL-language functions.
Fix for postgres_fdw when mapping a foreign table to a nontrivial remote view.
postgres_fdw no longer sends a FETCH FIRST WITH TIES clause to a remote server.

Log message:
revbump after icu and protobuf updates

Log message:
postgresql: updated to 16.3, 15.7, 14.12, 13.15, 12.19

PostgreSQL 16.3, 15.7, 14.12, 13.15, and 12.19

The PostgreSQL Global Development Group has released an update to all supported \ 
versions of PostgreSQL, including 16.3, 15.7, 14.12, 13.15, and 12.19. This \ 
release fixes one security vulnerability and over 55 bugs reported over the last \ 
several months.

A security vulnerability was found in the system views pg_stats_ext and \ 
pg_stats_ext_exprs, potentially allowing authenticated database users to see \ 
data they don't have sufficient privileges to view. The fix for this \ 
vulnerability only fixes fresh PostgreSQL installations, namely those that are \ 
created with the initdb utility after this fix is applied. If you have a current \ 
PostgreSQL installation and are concerned about this issue, please follow the \ 
instructions in the "Updating" section for remediation steps.

For the full list of changes, please review the release notes.