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:
databases/postgresql16: Fix krb5 defaults and dependencies.

Currently postgresql16's gssapi option requires mit-krb5.  It cannot
be safely linked, e.g. through libpq, into any application that also
links against a non-mit-krb5 libgssapi, such as heimdal as shipped in
NetBSD.

It is generally good to have gssapi support out of the box, since it
is probably the most widely deployed single-sign-on system on the
planet, and we've had it enabled by default for ages.  But it is now
incompatible with the default krb5 implementation in NetBSD and
pkgsrc on most platforms.  So, unless we can change pgsql to restore
heimdal support, this option has to be off unless you have switched
to mit-krb5 systemwide.

As discussed in this thread:

https://mail-index.netbsd.org/tech-pkg/2024/09/04/msg029866.html

Verified on NetBSD that:

- out of the box, gssapi is disabled by default
- with PKG_OPTIONS.postgresql16+=gssapi, PKG_FAIL_REASON fires
- with KRB5_DEFAULT=mit-krb5, gssapi is enabled by default

Also verified, with and without gssapi, that it builds a libpq.so
that does not link against /usr/lib/libgssapi.so (but with gssapi,
does link against mit-krb5's libgssapi_krb5.so).

Log message:
fix typo

Log message:
postgresql16: disable gssapi by default on Linux

Since it causes conflicts between heimdal and mit-krb5 in the default
pkgsrc configuration. Add some comments to explain why the normal
krb5 selection logic is not in use here.