Log message:
*: bump for llvm 19 (shlib major changed)

Log message:
postgresql: updated to 17.5, 16.9, 15.13, 14.18, 13.21

PostgreSQL 17.5, 16.9, 15.13, 14.18, and 13.21

CVE-2025-4207: PostgreSQL GB18030 encoding validation can read one byte past end \ 
of allocation for text that fails validation

Bug Fixes and Improvements

This update fixes over 60 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.

Handle self-referential foreign keys on partitioned tables correctly. Creating \ 
or attaching partitions failed to make the required catalog entries for a \ 
foreign-key constraint if the table referenced by the constraint was the same \ 
partitioned table. This resulted in failure to enforce the constraint fully. To \ 
fix this, please see the instructions in the "Updating" section.
Fix for potential data loss issue when using BRIN bloom indexes (e.g. using the \ 
date_bloom_ops operator class).
Fix MERGE into a partitioned table with DO NOTHING actions.
Prevent failure in INSERT commands when the table has a GENERATED column of a \ 
domain type and the domain's constraints disallow NULL values.
Fix ALTER TABLE .. ADD COLUMN to correctly handle the case of a domain type that \ 
has its own default value and the DEFAULT for the column is not set.
Fix issues when performing casts within the keys of JSON constructor expressions.
Fix XMLSERIALIZE() so that the INDENT option is correctly dumped out when it's \ 
present in views or rules. This was noticeable on restores.
Several query planner fixes, including avoiding a premature evaluation of \ 
arguments in an aggregate function that has both FILTER and either ORDER BY or \ 
DISTINCT clauses that could lead to unnecessary failures.
Fix for potentially returning incorrect results when a bitmap scan without \ 
output columns is executed while vacuum is also running on the same table.
Fix performance issues in GIN index search startup when there are many search \ 
keys, for example, jsonbcol ?| array[...] with tens of thousands of array \ 
elements.
Ensure that I/O statistics of active WAL senders are reported within at most one \ 
second.
Fix race condition in handling of synchronous_standby_names immediately after \ 
startup, where a backend might fail to wait for a synchronous commit.
Avoid infinite loop if scram_iterations is set to INT_MAX.
Several fixes for logical replication, including handling of vacuum around \ 
deleted rows that are still required for logical decoding.
Prevent potential data loss when schema modification operations (DDL) that don't \ 
take a strong lock affect tables that are being logically replicated.
Prevent issues in logical replication that could allow duplicate data to be \ 
applied due to apply worker error handling.
Improve how reindexdb handles scheduling parallel reindex operations to achieve \ 
the expected amount of parallelism.

This release also updates time zone data files to tzdata release 2025b for DST \ 
law changes in Chile, plus historical corrections for Iran. Additionally, there \ 
is a new time zone America/Coyhaique for Chile's Aysén Region, to account for \ 
it changing to UTC-03 year-round, which diverges from America/Santiago.

Log message:
postgresql16*: SOEXT -> SHLIB_EXT

Log message:
*: recursive bump for default Kerberos implementation switch

Log message:
*: recursive bump for icu 77 and libxml2 2.14

Log message:
*: remove MirBSD support

Log message:
postgres: many MAKE_JOBS issues remain, for example

fatal error: 'catalog/pg_type_d.h' file not found

Log message:
postgresql: updated to 17.4, 16.8, 15.12, 14.17, 13.20

PostgreSQL 17.4, 16.8, 15.12, 14.17, and 13.20

The issues listed below affect PostgreSQL 17. Some of these issues may also
affect other supported versions of PostgreSQL.

Improve behavior of quoting functions in libpq. The fix for CVE-2025-1094
caused the quoting functions to not honor their string length parameters and,
in some cases, cause crashes. This problem could be noticeable from a
PostgreSQL client library, based on how it is integrated with libpq.
Fix small memory leak in pg_createsubscriber.