Log message:
*: recursive bump for Python 3.11 as new default

Log message:
postgresql: updated to 15.3, 14.8, 13.11, 12.15, and 11.20

PostgreSQL 15.3, 14.8, 13.11, 12.15, and 11.20

Security Issues
CVE-2023-2454: CREATE SCHEMA ... schema_element defeats protective search_path \ 
changes.
CVE-2023-2455: Row security policies disregard user ID changes after inlining.

Bug Fixes and Improvements

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

Included in this release:

Several fixes for CREATE DATABASE when using the STRATEGY = WAL_LOG, including a \ 
potential corruption that could lose modifications to a template/source \ 
database.
Fix crash with CREATE SCHEMA AUTHORIZATION.
Several fixes for MERGE.
Several fixes for triggers in partitioned tables.
Disallow altering composite types that are stored in indexes.
Ensure that COPY TO from a parent table with row-level security enabled does not \ 
copy any rows from child tables.
Adjust text-search-related character classification logic to correctly detect \ 
whether the prevailing locale is C when the default collation of a database uses \ 
the ICU provider.
Re-allow exponential notation in ISO-8601 interval fields.
Improve error reporting for various invalid JSON string literals.
Fix data corruption due to vacuum_defer_cleanup_age being larger than the \ 
current 64-bit xid.
Several fixes for the query parser and planner, including better detection of \ 
improperly-nested aggregates.
Fix partition pruning bug with the boolean IS NOT TRUE and IS NOT FALSE \ 
conditions. Prior to this, NULL partitions were accidentally pruned.
Fix memory leak in memoize plan execution.
Fix buffer refcount leak on foreign tables using partitions when performing \ 
batched inserts.
Restore support for sub-millisecond vacuum_cost_delay settings.
Several fixes for views and rules.
Avoid unnecessary work while scanning a multi-column BRIN index with multiple \ 
scan keys.
Ignore dropped columns and generated columns during logical replication of an \ 
UPDATE or DELETE action.
Several fixes for naming and availability of wait events.
Support RSA-PSS certificates with SCRAM-SHA-256 channel binding. This feature \ 
requires building with OpenSSL 1.1.1 or newer.
Avoid race condition with process ID tracking on Windows.
Fix memory leak within a session for PL/pgSQL DO blocks that use cast expressions.
Tighten array dimensionality checks from PL/Perl and PL/Python when converting \ 
list structures to multi-dimensional SQL arrays.
Fix pg_dump so that partitioned tables that are hash-partitioned on an \ 
enumerated type column can be restored successfully.
Fix for pg_trgm where an unsatisfiable regular expression could lead to a crash \ 
when using a GiST or GIN index.
Limit memory usage of pg_get_wal_records_info() in pg_walinspect.

Log message:
revbump after textproc/icu update

Log message:
postgresql: updated to 15.2, 14.7, 13.10, 12.14, and 11.19

Security Issues

CVE-2022-41862: Client memory disclosure when connecting, with Kerberos, to \ 
modified server.

Versions Affected: 12 - 15.

A modified, unauthenticated server or an unauthenticated man-in-the-middle can \ 
send an unterminated string during the establishment of Kerberos transport \ 
encryption. When a libpq client application has a Kerberos credential cache and \ 
doesn't explicitly disable option gssencmode, a server can cause libpq to \ 
over-read and report an error message containing uninitialized bytes from and \ 
following its receive buffer. If libpq's caller somehow makes that message \ 
accessible to the attacker, this achieves a disclosure of the over-read bytes. \ 
We have not confirmed or ruled out viability of attacks that arrange for a crash \ 
or for presence of notable, confidential information in disclosed bytes.

The PostgreSQL project thanks Jacob Champion for reporting this problem.

Bug Fixes and Improvements

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

Included in this release:

Fix for partitioned tables to correctly update GENERATED columns in child tables \ 
if the GENERATED column does not exist in the parent table or the child \ 
generated column has different dependencies than the parent.
Several fixes for the MERGE command.
Allow a WITH RECURSIVE ... CYCLE query to access its SET output column.
Fix an issue with bulk insertions on foreign tables that could lead to logical \ 
inconsistencies, for example, a BEFORE ROW trigger may not process rows that \ 
should be available.
Reject uses of undefined variables in jsonpath existence checks.
Fix for jsonb subscripting that come directly from a text column in a table.
Honor updated values of checkpoint_completion_target on reload.
Log the correct ending timestamp in recovery_target_xid mode.
Fix issue to allow column lists longer than 100 when using logical replication.
Prevent "wrong tuple length" failure at the end of VACUUM.
Avoid an immediate commit after ANALYZE when using query pipelining.
Several fixes to the query planner, including one that provides more \ 
opportunities for using memoization with partitionwise joins.
Fix for statistics collection to correctly handle when a relation changes type \ 
(e.g. a table is converted to a view).
Ensure full text search queries can be cancelled while performing phrase matches.
Fix deadlock between DROP DATABASE and logical replication worker process.
Fix small session-lifespan memory leak when CREATE SUBSCRIPTION fails its \ 
connection attempt.
Performance improvement for replicas with hot_standby enabled that are \ 
processing SELECT queries.
Several fixes for logical decoding that improve its stability and bloat handling.
Fix the default logical replication plug-in, pgoutput, to not send columns that \ 
are not listed in a table's replication column list.
Fix possible corruption of very large tablespace map files in pg_basebackup.
Remove a harmless warning from pg_dump in --if-exists mode when the public \ 
schema has a non-default owner.
Fix the psql commands \sf and \ef to handle SQL-language functions that have \ 
SQL-standard function bodies (i.e. BEGIN ATOMIC).
Fix tab completion of ALTER FUNCTION/PROCEDURE/ROUTINE ... SET SCHEMA.
Update the pageinspect extension to mark its disk-accessing functions as \ 
PARALLEL RESTRICTED.
Fix the seg extension to not crash or print garbage if an input number has more \ 
than 127 digits.

Log message:
massive revision bump after textproc/icu update

Log message:
postgresql: updated to 14.5, 13.8, 12.12, 11.17, 10.22

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

Included in this release:

Fix replay of CREATE DATABASE write-ahead log (WAL) records on standby servers \ 
when encountering a missing tablespace directory.
Add support for tablespaces that are plain directories instead of symbolic links \ 
to other directories.
Fix permission checks in CREATE INDEX to use the user's permissions. This fixes \ 
broken dump/restore scenarios that relied on the behavior prior to the fix for \ 
CVE-2022-1552.
In the extended query protocol, force an immediate commit after CREATE DATABASE \ 
and other commands that can't run in a transaction block.
Fix a race condition around checking transaction visibility that was more likely \ 
to happen when using synchronous replication.
Fix incorrect permission-checking code for extended statistics.
Fix extended statistics machinery to handle most common value (MCV)-type \ 
statistics on boolean-valued expressions.
Avoid planner core dump with constant = ANY(array) clauses when there are \ 
MCV-type extended statistics on the array variable.
Allow cancellation of ANALYZE while it is computing extended statistics.
Fix ALTER TABLE ... ENABLE/DISABLE TRIGGER to handle recursion for triggers on \ 
partitioned tables.
Reject ROW() expressions and functions in FROM that have more than 1600 columns.
Fix memory leak in logical replication subscribers.
Fix checks in logical replication of replica identity when the target table is \ 
partitioned.
Arrange to clean up after commit-time errors within SPI_commit(), rather than \ 
expecting callers to do that. This includes a fix for the same scenario in \ 
PL/Python, which had reported crashes on Python 3.11 and memory leaks on older \ 
versions of Python 3.
Improve handling in libpq of idle states in pipeline mode.
In the psql \watch command, echo a newline after cancellation with control-C.
Fix pg_upgrade to detect non-upgradable usages of functions accepting anyarray \ 
parameters.
Several postgres_fdw fixes, including prevention of batch insertions when there \ 
are WITH CHECK OPTION constraints present.

Log message:
*: Revbump packages that use Python at runtime without a PKGNAME prefix

Log message:
*: recursive bump for perl 5.36

Log message:
postgresqlNN: updated to 14.3, 13.7, 12.11, 11.16, and 10.21

The PostgreSQL Global Development Group has released an update to all supported \ 
versions of PostgreSQL, including 14.3, 13.7, 12.11, 11.16, and 10.21. This \ 
release closes one security vulnerability and fixes over 50 bugs reported over \ 
the last three months.

CVE-2022-1552: Autovacuum, REINDEX, and others omit "security restricted \ 
operation" sandbox.

Versions Affected: 10 - 14. The security team typically does not test \ 
unsupported versions, but this problem is quite old.

Autovacuum, REINDEX, CREATE INDEX, REFRESH MATERIALIZED VIEW, CLUSTER, and \ 
pg_amcheck made incomplete efforts to operate safely when a privileged user is \ 
maintaining another user's objects. Those commands activated relevant \ 
protections too late or not at all. An attacker having permission to create \ 
non-temp objects in at least one schema could execute arbitrary SQL functions \ 
under a superuser identity.

While promptly updating PostgreSQL is the best remediation for most users, a \ 
user unable to do that can work around the vulnerability by disabling \ 
autovacuum, not manually running the above commands, and not restoring from \ 
output of the pg_dump command. Performance may degrade quickly under this \ 
workaround. VACUUM is safe, and all commands are fine when a trusted user owns \ 
the target object.

Bug Fixes and Improvements

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

Included in this release:

Fix issue that could lead to corruption of GiST indexes on ltree columns. After \ 
upgrading, you will need to reindex any GiST indexes on ltree columns.
Column names in tuples produced by a whole-row variable (e.g. tbl.*) outside of \ 
a top-level of a SELECT list are now always associated with those of the \ 
associated named composite type, if there is one. The release notes detail a \ 
workaround if you depend on the previous behavior.
Fix incorrect rounding when extracting epoch values from interval types.
Prevent issues with calling pg_stat_get_replication_slot(NULL).
Fix incorrect output for types timestamptz and timetz in table_to_xmlschema().
Fix errors related to a planner issue that affected asynchronous remote queries.
Fix planner failure if a query using SEARCH or CYCLE features contains a \ 
duplicate common-table expression (WITH) name.
Fix ALTER FUNCTION to support changing a function's parallelism property and its \ 
SET-variable list in the same command.
Fix incorrect sorting of table rows when using CLUSTER on an index whose leading \ 
key is an expression.
Prevent data loss if a system crash occurs shortly after a sorted GiST index build.
Fix risk of deadlock failures while dropping a partitioned index.
Fix race condition between DROP TABLESPACE and checkpointing that could fail to \ 
remove all dead files from the tablespace directory.
Fix potential issue in crash recovery after a TRUNCATE command that overlaps \ 
with a checkpoint.
Re-allow _ as the first character in a custom configuration parameter name.
Fix PANIC: xlog flush request is not satisfied failure during standby promotion \ 
when there is a missing WAL continuation record.
Fix possibility of self-deadlock in hot standby conflict handling.
Ensure that logical replication apply workers can be restarted when the server \ 
is near the max_sync_workers_per_subscription limit.
Disallow execution of SPI functions during PL/Perl function compilation.
libpq now accepts root-owned SSL private key files, which matches the rules the \ 
server has used since the 9.6 release.
Re-allow database.schema.table patterns in psql, pg_dump, and pg_amcheck.
Several fixes for pageinspect to improve overall stability.
Disable batch insertion in postgres_fdw when BEFORE INSERT ... FOR EACH ROW \ 
triggers exist on the foreign table.
Update JIT code to work with LLVM 14.

Log message:
Add lz4 to postgresql14 options (enabled by default)

Bump PKGREVISION on all including packages just to be on the safe side