Log message:
postgresql13: PLIST fix for gssapi option turned off

Log message:
postgresql: fix buildling contrib/uuid-ossp; fixes for LLVM enabled; should fix \ 
#55803

Log message:
postgresql: updated to 13.2, 12.6, 11.11, 10.16, 9.6.21, and 9.5.25

The PostgreSQL Global Development Group has released an update to all supported \ 
versions of our database system, including 13.2, 12.6, 11.11, 10.16, 9.6.21, and \ 
9.5.25. This release closes two security vulnerabilities and fixes over 80 bugs \ 
reported over the last three months.

Additionally, this is the final release of PostgreSQL 9.5. If you are running \ 
PostgreSQL 9.5 in a production environment, we suggest that you make plans to \ 
upgrade.

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

Security Issues

CVE-2021-3393: Partition constraint violation errors leak values of denied columns

Versions Affected: 11 - 13.

A user having an UPDATE privilege on a partitioned table but lacking the SELECT \ 
privilege on some column may be able to acquire denied-column values from an \ 
error message. This is similar to CVE-2014-8161, but the conditions to exploit \ 
are more rare.

The PostgreSQL project thanks Heikki Linnakangas for reporting this problem.

CVE-2021-20229: Single-column SELECT privilege enables reading all columns

Versions Affected: 13.

A user having a SELECT privilege on an individual column can craft a special \ 
query that returns all columns of the table.

Additionally, a stored view that uses column-level privileges will have \ 
incomplete column-usage bitmaps. In installations that depend on column-level \ 
permissions for security, it is recommended to execute CREATE OR REPLACE on all \ 
user-defined views to force them to be re-parsed.

The PostgreSQL project thanks Sven Klemm for reporting this problem.

Bug Fixes and Improvements

This update fixes over 80 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 an issue with GiST indexes where concurrent insertions could lead to a \ 
corrupt index with entries placed in the wrong pages. You should REINDEX any \ 
affected GiST indexes.
Fix CREATE INDEX CONCURRENTLY to ensure rows from concurrent prepared \ 
transactions are included in the index. Installations that have enabled prepared \ 
transactions should REINDEX any concurrently-built indexes.
Fix for possible incorrect query results when a hash aggregation is spilled to disk.
Fix edge case in incremental sort that could lead to sorting results incorrectly \ 
or a "retrieved too many tuples in a bounded sort" error.
Avoid crash when a CALL or DO statement that performs a transaction rollback is \ 
executed via extended query protocol, such as from prepared statements.
Fix a failure when a PL/pgSQL procedure used CALL on another procedure that has \ 
OUT parameters that executed a COMMIT or ROLLBACK.
Remove errors from BEFORE UPDATE triggers on partitioned tables for restrictions \ 
that no longer apply.
Several fixes for queries with joins that could lead to error messages such as \ 
"no relation entry for relid N" or "failed to build any N-way \ 
joins".
Do not consider parallel-restricted or set-returning functions in an ORDER BY \ 
expressions when trying to parallelize sorts.
Fix ALTER DEFAULT PRIVILEGES to handle duplicate arguments safely.
Several fixes in behavior when wal_level is set to minimal, including when \ 
tables are rewritten within a transaction.
Several fixes for CREATE TABLE LIKE.
Ensure that allocated disk space for a dropped relation (e.g. a table) is \ 
released promptly when a transaction is committed.
Fix progress reporting for CLUSTER.
Fix handling of backslash-escaped multibyte characters in COPY FROM.
Fix recently-introduced race conditions in LISTEN/NOTIFY queue handling.
Allow the jsonb concatenation operator (||) to handle all combinations of JSON \ 
data types.
Fix WAL-reading logic so that standbys can handle timeline switches correctly. \ 
This issue could have shown itself with errors like "requested WAL segment \ 
has already been removed".
Several leak fixes for the walsender process around logical decoding and replication.
Ensure that a nonempty value of krb_server_keyfile always overrides any setting \ 
of KRB5_KTNAME in the server environment
Several fixes for GSS encryption support.
Ensure the \connect command allows the use of a password in the \ 
connection_string argument.
Fix assorted bugs with the \help command.
Several fixes for pg_dump.
Ensure that pg_rewind accounts for all WAL when rewinding a standby server.
Fix memory leak in contrib/auto_explain.
Ensure all postgres_fdw connections are closed if the a user mapping or foreign \ 
server object those connections depend on are dropped.
Fix JIT compilation to be compatible with LLVM 11 and LLVM 12.
This update also contains tzdata release 2021a for DST law changes in Russia \ 
(Volgograd zone) and South Sudan, plus historical corrections for Australia, \ 
Bahamas, Belize, Bermuda, Ghana, Israel, Kenya, Nigeria, Palestine, Seychelles, \ 
and Vanuatu.

Notably, the Australia/Currie zone has been corrected to the point where it is \ 
identical to Australia/Hobart.

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

PostgreSQL 9.5 is EOL

This is the final release of PostgreSQL 9.5. If you are running PostgreSQL 9.5 \ 
in a production environment, we suggest that you make plans to upgrade to a \ 
newer, supported version of PostgreSQL. Please see our versioning policy for \ 
more information.

Log message:
Revbump for openpam cppflags change months ago, belatedly.

Log message:
postgresql: updated to 13.1, 12.5, 11.10, 10.15, 9.6.20, and 9.5.24

PostgreSQL 13.1, 12.5, 11.10, 10.15, 9.6.20, and 9.5.24

Security Issues

* CVE-2020-25695: Multiple features escape "security restricted \ 
operation" sandbox
* CVE-2020-25694: Reconnection can downgrade connection security settings
* CVE-2020-25696: psql's \gset allows overwriting specially treated variables

Bug Fixes and Improvements

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

Some of these fixes include:

Fix a breakage in the replication protocol by ensuring that two "command \ 
completion" events are expected for START_REPLICATION.
Ensure fsync is called on the SLRU caches that PostgreSQL maintains. This \ 
prevents potential data loss due to an operating system crash.
Fix ALTER ROLE usage for users with the BYPASSRLS permission.
ALTER TABLE ONLY ... DROP EXPRESSION is disallowed on partitioned tables when \ 
there are child tables.
Ensure that ALTER TABLE ONLY ... ENABLE/DISABLE TRIGGER does not apply to child \ 
tables.
Fix for ALTER TABLE ... SET NOT NULL on partitioned tables to avoid a potential \ 
deadlock in parallel pg_restore.
Fix handling of expressions in CREATE TABLE LIKE with inheritance.
DROP INDEX CONCURRENTLY is disallowed on partitioned tables.
Allow LOCK TABLE to succeed on a self-referential view instead of throwing an error.
Several fixes around statistics collection and progress reporting for REINDEX \ 
CONCURRENTLY.
Ensure that GENERATED columns are updated when any columns they depend on are \ 
updated via a rule or an updatable view.
Support hash partitioning with text array columns as partition keys.
Allow the jsonpath .datetime() method to accept ISO 8601-format timestamps.
During a "smart" shutdown, ensure background processes are not \ 
terminated until all foreground client sessions are completed, fixing an issue \ 
that broke the processing of parallel queries.
Several fixes for the query planner and optimizer.
Ensure that data is de-toasted before being inserted into a BRIN index. This \ 
could manifest itself with errors like "missing chunk number 0 for toast \ 
value NNN". If you have seen a similar error in an existing BRIN index, you \ 
should be able to correct it by using REINDEX on the index.
Fix the output of EXPLAIN to have the correct XML tag nesting for incremental \ 
sort plans.
Several fixes for memory leaks, including ones involving RLS policies, using \ 
CALL with PL/pgSQL, SIGHUP processing a configuration parameter that cannot be \ 
applied without a restart, and an edge-case for index lookup for a partition.
libpq can now support arbitrary-length lines in the .pgpass file.
On Windows, psql now reads the output of a backtick command in text mode, not \ 
binary mode, so it can now properly handle newlines.
Fix how pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb use complex \ 
connection-string parameters.
When the \connect command of psql reuses connection parameters, ensure that all \ 
non-overridden parameters from a previous connection string are also re-used.
Ensure that pg_dump collects per-column information about extension \ 
configuration tables, avoiding crashes when specifying --inserts.
Ensure that parallel pg_restore processes foreign keys referencing partitioned \ 
tables in the correct order.
Several fixes for contrib/pgcrypto, including a memory leak fix.

Log message:
*: Recursive revbump from textproc/icu-68.1

Log message:
postgresql13: added version 13.0

PostgreSQL 13 contains many new features and enhancements, including:
* Space savings and performance gains from de-duplication of B-tree index entries
* Improved performance for queries that use aggregates or partitioned tables
* Better query planning when using extended statistics
* Parallelized vacuuming of indexes
* Incremental sorting