Log message:
postgresql13-client: Mark MAKE_JOBS_SAFE=no.

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:
postgresql*-client: Use OPSYS_VERSION to numerically compare NetBSD versions

XXX do we still want to keep hacks for NetBSD 3?

Log message:
revbump for textproc/icu update

Log message:
postgresql1N: updated to 14.2, 13.6, 12.10, 11.15, and 10.20

PostgreSQL 14.2, 13.6, 12.10, 11.15, and 10.20 Released!

This update fixes over 55 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 for a low probability scenario of index corruption when a HOT (heap-only \ 
tuple) chain changes state during VACUUM. Encountering this issue is unlikely, \ 
but if you are concerned, please consider reindexing.
Fix for using REINDEX CONCURRENTLY on TOAST table indexes to prevent corruption. \ 
You can fix any TOAST indexes by reindexing them again.
The psql \password command now defaults to setting the password for the role \ 
defined by CURRENT_USER. Additionally, the role name is now included in the \ 
password prompt.
Build extended statistics for partitioned tables. If you previously added \ 
extended statistics to a partitioned table, you should run ANALYZE on those \ 
tables. As autovacuum currently does not process partitioned tables, you must \ 
periodically run ANALYZE on any partitioned tables to update their statistics.
Fix crash with ALTER STATISTICS when the statistics object is dropped concurrently.
Fix crash with multiranges when extracting variable-length data types.
Several fixes to the query planner that lead to incorrect query results.
Several fixes for query plan memoization.
Fix startup of a physical replica to tolerate transaction ID wraparound.
When using logical replication, avoid duplicate transmission of a partitioned \ 
table's data when the publication includes both the child and parent tables.
Disallow altering data type of a partitioned table's columns when the \ 
partitioned table's row type is used as a composite type elsewhere.
Disallow ALTER TABLE ... DROP NOT NULL for a column that is part of a replica \ 
identity index.
Several fixes for caching that correct logical replication behavior and improve \ 
performance.
Fix memory leak when updating expression indexes.
Avoid leaking memory during REASSIGN OWNED BY operations that reassign ownership \ 
of many objects.
Fix display of whole-row variables appearing in INSERT ... VALUES rules.
Fix race condition that could lead to failure to localize error messages that \ 
are reported early in multi-threaded use of libpq or ecpglib.
Fix psql \d command for identifying parent triggers.
Fix failures on Windows when using the terminal as data source or destination. \ 
This affected the psql \copy command and using pg_recvlogical with -f -.
Fix the pg_dump --inserts and --column-inserts modes to handle tables that \ 
contain both generated and dropped columns.
Fix edge cases in how postgres_fdw handles asynchronous queries. These errors \ 
could lead to crashes or incorrect results when attempting to run parallel scans \ 
of foreign tables.
For the full list of changes available, please review the release notes.

Log message:
revbump for icu and libffi

Log message:
postgresql: updated to 14.1, 13.5, 12.9, 11.14, 10.19, 9.6.24

PostgreSQL 14.1, 13.5, 12.9, 11.14, 10.19, and 9.6.24

Security Issues

CVE-2021-23214: Server processes unencrypted bytes from man-in-the-middle

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

When the server is configured to use trust authentication with a clientcert \ 
requirement or to use cert authentication, a man-in-the-middle attacker can \ 
inject arbitrary SQL queries when a connection is first established, despite the \ 
use of SSL certificate verification and encryption.

The PostgreSQL project thanks Jacob Champion for reporting this problem.

CVE-2021-23222: libpq processes unencrypted bytes from man-in-the-middle

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

A man-in-the-middle attacker can inject false responses to the client's first \ 
few queries, despite the use of SSL certificate verification and encryption.

If more preconditions hold, the attacker can exfiltrate the client's password or \ 
other confidential data that might be transmitted early in a session. The \ 
attacker must have a way to trick the client's intended server into making the \ 
confidential data accessible to the attacker. A known implementation having that \ 
property is a PostgreSQL configuration vulnerable to CVE-2021-23214.

As with any exploitation of CVE-2021-23214, the server must be using trust \ 
authentication with a clientcert requirement or using cert authentication. To \ 
disclose a password, the client must be in possession of a password, which is \ 
atypical when using an authentication configuration vulnerable to \ 
CVE-2021-23214. The attacker must have some other way to access the server to \ 
retrieve the exfiltrated data (a valid, unprivileged login account would be \ 
sufficient).

The PostgreSQL project thanks Jacob Champion for reporting this problem.

Bug Fixes and Improvements

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.

Some of these fixes include:

Fix physical replication for cases where the primary crashes after shipping a \ 
WAL segment that ends with a partial WAL record. When applying this update, \ 
update your standby servers before the primary so that they will be ready to \ 
handle the fix if the primary happens to crash.
Fix parallel VACUUM so that it will process indexes below the \ 
min_parallel_index_scan_size threshold if the table has at least two indexes \ 
that are above that size. This problem does not affect autovacuum. If you are \ 
affected by this issue, you should reindex any manually-vacuumed tables.
Fix causes of CREATE INDEX CONCURRENTLY and REINDEX CONCURRENTLY writing corrupt \ 
indexes. You should reindex any concurrently-built indexes.
Fix for attaching/detaching a partition that could allow certain INSERT/UPDATE \ 
queries to misbehave in active sessions.
Fix for creating a new range type with CREATE TYPE that could cause problems for \ 
later event triggers or subsequent executions of the CREATE TYPE command.
Fix updates of element fields in arrays of a domain that is a part of a composite.
Disallow the combination of FETCH FIRST WITH TIES and FOR UPDATE SKIP LOCKED.
Fix corner-case loss of precision in the numeric power() function.
Fix restoration of a Portal's snapshot inside a subtransaction, which could lead \ 
to a crash. For example, this could occur in PL/pgSQL when a COMMIT is \ 
immediately followed by a BEGIN ... EXCEPTION block that performs a query.
Clean up correctly if a transaction fails after exporting its snapshot. This \ 
could occur if a replication slot was created then rolled back, and then another \ 
replication slot was created in the same session.
Fix for "overflowed-subtransaction" wraparound tracking on standby \ 
servers that could lead to performance degradation.
Ensure that prepared transactions are properly accounted for during promotion of \ 
a standby server.
Ensure that the correct lock level is used when renaming a table.
Avoid crash when dropping a role that owns objects being dropped concurrently.
Disallow setting huge_pages to on when shared_memory_type is sysv
Fix query type checking in the PL/pgSQL RETURN QUERY.
Several fixes for pg_dump, including the ability to dump non-global default \ 
privileges correctly.
Use the CLDR project's data to map Windows time zone names to IANA time zones.
This update also contains tzdata release 2021e for DST law changes in Fiji, \ 
Jordan, Palestine, and Samoa, plus historical corrections for Barbados, Cook \ 
Islands, Guyana, Niue, Portugal, and Tonga.

Also, the Pacific/Enderbury zone has been renamed to Pacific/Kanton. Also, the \ 
following zones have been merged into nearby, more-populous zones whose clocks \ 
have agreed with them since 1970: Africa/Accra, America/Atikokan, \ 
America/Blanc-Sablon, America/Creston, America/Curacao, America/Nassau, \ 
America/Port_of_Spain, Antarctica/DumontDUrville, and Antarctica/Syowa. In all \ 
these cases, the previous zone name remains as an alias.

Log message:
postgresql: updated to 13.4, 12.8, 11.13, 10.18, 9.6.23

PostgreSQL 13.4, 12.8, 11.13, 10.18, 9.6.23

Security Issues

CVE-2021-3677: Memory disclosure in certain queries

Versions Affected: 11 - 13.

A purpose-crafted query can read arbitrary bytes of server memory. In the \ 
default configuration, any authenticated database user can complete this attack \ 
at will. The attack does not require the ability to create objects. If server \ 
settings include max_worker_processes=0, the known versions of this attack are \ 
infeasible. However, undiscovered variants of the attack may be independent of \ 
that setting.

Bug Fixes and Improvements

This update also fixes over 75 bugs that were reported in the last several \ 
months. Some of these issues affect only version 13, but many affect all \ 
supported versions.

Some of these fixes include:

Completely disable TLS/SSL renegotiation. This was previously disabled, but the \ 
server would still execute a client-initiated renegotiation request.
Restore the Portal-level snapshot after COMMIT or ROLLBACK within a procedure. \ 
This change fixes cases where an attempt to fetch a toasted value immediately \ 
after COMMIT/ROLLBACK would fail with errors like "no known snapshots" \ 
or "missing chunk number 0 for toast value".
Avoid misbehavior when persisting the output of a cursor that's reading a \ 
volatile query.
Reject cases where a query in WITH rewrites to just NOTIFY, which would cause a \ 
crash.
Several corner-case fixes for numeric types.
ALTER EXTENSION now locks the extension when adding or removing a member object.
The "enabled" status is now copied when a partitioned table's triggers \ 
are cloned to a new partition.
Avoid alias conflicts in queries generated for REFRESH MATERIALIZED VIEW \ 
CONCURRENTLY. This command failed on materialized views containing columns with \ 
certain names, notably mv and newdata.
Disallow whole-row variables in GENERATED expressions.
Several fixes for DROP OWNED BY behavior in relation to row-level security (RLS) \ 
policies.
Re-allow old-style Windows locale names in CREATE COLLATION commands.
walsenders now show their latest replication command in pg_stat_activity, \ 
instead of just showing the latest SQL command.
pg_settings.pending_restart now shows as true when a pertinent entry in \ 
postgresql.conf is removed.
On 64-bit Windows, allow the effective value of work_mem * hash_mem_multiplier \ 
to exceed 2GB.
Update minimum recovery point when WAL replay of a transaction abort record \ 
causes file truncation.
Advance oldest-required-WAL-segment horizon properly after a replication slot is \ 
invalidated. This fixes an issue where the server's WAL storage could run out of \ 
space.
Improve progress reporting for the sort phase of a parallel B-tree index build.
Fix assorted crash cases in logical replication of partitioned-table updates and \ 
when firing AFTER triggers of partitioned tables.
Prevent infinite loops in SP-GiST index insertion.
Ensure that SP-GiST index insertion can be terminated by a query cancel request.
In psql and other client programs, avoid overrunning the ends of strings when \ 
dealing with invalidly-encoded data.
Fix pg_dump to correctly handle triggers on partitioned tables whose enabled \ 
status is different from their parent triggers' status.
Avoid "invalid creation date in header" warnings when running \ 
pg_restore on a file created in a different time zone.
pg_upgrade now carries forward the old installation's oldestXID value and no \ 
longer forces an anti-wraparound VACUUM."
Extend pg_upgrade to detect and warn about extensions that should be upgraded.
Fix contrib/postgres_fdw to better work with generated columns, so long as a \ 
generated column in a foreign table represents a generated column in the remote \ 
table.

Log message:
*: recursive bump for perl 5.34

Log message:
postgresql: updated to 13.3, 12.7, 11.12, 10.17, 9.6.22

PostgreSQL 13.3, 12.7, 11.12, 10.17, and 9.6.22 Released!

Posted on 2021-05-13 by PostgreSQL Global Development Group
 PostgreSQL Project  Security
The PostgreSQL Global Development Group has released an update to all supported \ 
versions of our database system, including 13.3, 12.7, 11.12, 10.17, and 9.6.22. \ 
This release closes three security vulnerabilities and fixes over 45 bugs \ 
reported over the last three months.

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

Security Issues

CVE-2021-32027: Buffer overrun from integer overflow in array subscripting \ 
calculations

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

While modifying certain SQL array values, missing bounds checks let \ 
authenticated database users write arbitrary bytes to a wide area of server \ 
memory.

The PostgreSQL project thanks Tom Lane for reporting this problem.

CVE-2021-32028: Memory disclosure in INSERT ... ON CONFLICT ... DO UPDATE

Versions Affected: 9.6 - 13. The security team typically does not test \ 
unsupported versions. The feature first appeared in 9.5.

Using an INSERT ... ON CONFLICT ... DO UPDATE command on a purpose-crafted \ 
table, an attacker can read arbitrary bytes of server memory. In the default \ 
configuration, any authenticated database user can create prerequisite objects \ 
and complete this attack at will. A user lacking the CREATE and TEMPORARY \ 
privileges on all databases and the CREATE privilege on all schemas cannot use \ 
this attack at will.

The PostgreSQL project thanks Andres Freund for reporting this problem.

CVE-2021-32029: Memory disclosure in partitioned-table UPDATE ... RETURNING

Versions Affected: 11 - 13

Using an UPDATE ... RETURNING on a purpose-crafted partitioned table, an \ 
attacker can read arbitrary bytes of server memory. In the default \ 
configuration, any authenticated database user can create prerequisite objects \ 
and complete this attack at will. A user lacking the CREATE and TEMPORARY \ 
privileges on all databases and the CREATE privilege on all schemas typically \ 
cannot use this attack at will.

The PostgreSQL project thanks Tom Lane for reporting this problem.

Bug Fixes and Improvements

This update fixes over 45 bugs that were reported in the last several months. \ 
Some of these issues only affect version 13, but could also apply to other \ 
supported versions.

Some of these fixes include:

Fix potential incorrect computation of UPDATE ... RETURNING outputs for joined, \ 
cross-partition updates.
Fix ALTER TABLE ... ALTER CONSTRAINT when used on foreign-key constraints on \ 
partitioned tables. The command would fail to adjust the DEFERRABLE and/or \ 
INITIALLY DEFERRED properties of the constraints and triggers of leaf \ 
partitions, leading to unexpected behavior. After updating to this version, you \ 
can execute the ALTER TABLE ... ALTER CONSTRAINT command to fix any misbehaving \ 
partitioned tables.
Ensure that when a child table is attached with ALTER TABLE ... INHERIT that \ 
generated columns in the parent are generated in the same way in the child.
Forbid marking an identity column as NULL.
Allow ALTER ROLE ... SET/ALTER DATABASE ... SET to set the role, \ 
session_authorization, and temp_buffers parameters.
Ensure that REINDEX CONCURRENTLY preserves any statistics target set for the index.
Fix an issue where, in some cases, saving records within AFTER triggers could \ 
cause crashes.
Fix how to_char() handles Roman-numeral month format codes with negative intervals.
Fix use of uninitialized value while parsing an \{m,n\} quantifier in a BRE-mode \ 
regular expression.
Fix "could not find pathkey item to sort" planner errors that occur in \ 
some situations when the sort key involves an aggregate or window function.
Fix issue with BRIN index bitmap scans that could lead to "could not open \ 
file" errors.
Fix potentially wrong answers from GIN tsvector index searches when there are \ 
many matching records.
Fixes for COMMIT AND CHAIN functionality on both the server and psql.
Avoid incorrect timeline change while recovering uncommitted two-phase \ 
transactions from WAL, which could lead to consistency issues and the inability \ 
to restart the server.
Ensure thatwal_sync_method is set to fdatasync by default on newer FreeBSD releases.
Disable the vacuum_cleanup_index_scale_factor parameter and storage option.
Fix several memory leaks in the server, including one with SSL/TLS parameter \ 
initialization.
Restore the previous behavior of \connect service=XYZ to psql, i.e. disallow \ 
environmental variables (e.g. PGPORT) from overriding entries in the service \ 
file.
Fix how pg_dump handles generated columns in partitioned tables.
Add additional checks to pg_upgrade for user tables containing non-upgradable \ 
data types.
On Windows, initdb now prints instructions about how to start the server with \ 
pg_ctl using backslash separators.
Fix pg_waldump to count XACT records correctly when generating per-record statistics.