Log message:
postgresql1[0-5]: Updated to 15.1, 14.6, 13.9, 12.13, 11.18, and 10.23

PostgreSQL 15.1, 14.6, 13.9, 12.13, 11.18, and 10.23 Released!

Bug Fixes and Improvements

This update fixes over 25 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 updatable views for INSERT statements that include multi-row VALUES \ 
clauses with a DEFAULT set.
Disallow rules named _RETURN that are not ON SELECT rules.
Disallow use of MERGE on a partitioned table that has foreign-table partitions.
Fix for construction of per-partition foreign key constraints while doing ALTER \ 
TABLE ... ATTACH PARTITION, where previously incorrect or duplicate constraints \ 
could be built.
Fix for a planner failure with extended statistics on partitioned or inherited \ 
tables.
Fix bugs in logical decoding that could lead to memory leaks when replay starts \ 
from a point between the beginning of a transaction and the beginning of its \ 
subtransaction.
Fix issues with slow shutdown of replication workers by allowing interrupts in \ 
more places.
Disallow logical replication into foreign-table partitions.
Prevent crash in replication works after a SQL or PL/pgSQL function syntax error.
psql -c now exits with a nonzero status if the query is canceled.
Allow cross-platform tablespace relocation in pg_basebackup.
Fix pg_dump to include comments attached to some CHECK constraints.

Log message:
databases/postgresql*: Work around autoconf mkdir bug

autoconf does not accept NetBSD mkdir (this bug has already been fixed
in upstream autoconf).  This leads to install.sh, and thus
postgresql's workaround for a relative path in pgxs, and then that
being used in postgis.  Somewhere in that chain there is a bug leading
to postgis failing to make a directory at install time.

This passes in an autoconf cache variable so that for mkdir it uses
mkdir (which it does on GNU/Linux, and thus that situation is
well-tested).

Log message:
posgresql*: Restore MAKE_JOBS_SAFE=no

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:
*: Remove hardcoded -liconv / -lintl on SunOS.

This is now handled centrally via OPSYS_EXPLICIT_LIBDEPS support in libiconv
and gettext-lib.

Log message:
postgresql*-client: fix installed PGXS Makefiles when using pkgsrc gettext

If we are using the "nls" PKG_OPTION together with pkgsrc gettext, then
we must ensure CPPFLAGS contains -I${PREFIX}/include/gettext.
The installed postgresql/server/c.h expects to be able to include
<libintl.h> using the CPPFLAGS that get installed in Makefile.global.
Without this it is not possible to develop PGXS extensions
outside of pkgsrc.

Log message:
*: recursive bump for perl 5.36

Log message:
postgresql*: Mark unsafe for MAKE_JOBS

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:
revbump for textproc/icu update