![[BACK]](/icons/back.gif){kind=icon}
Up to [cvs.NetBSD.org] / pkgsrc / databases / postgresql15-pltcl
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
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.
*: recursive bump for default Kerberos implementation switch
*: recursive bump for icu 77 and libxml2 2.14
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
*: recursive bump for icu 76 shlib major version bump
*: revbump for icu downgrade
*: recursive bump for icu 76.1 shlib bump
postgresql: updated to 16.4, 15.8, 14.13, 13.16, 12.20 CVE-2024-7348: PostgreSQL relation replacement during pg_dump executes arbitrary SQL CVSS v3.1 Base Score: 8.8 Supported, Vulnerable Versions: 12 - 16. An attacker able to create and drop non-temporary objects could inject SQL code that would be executed by a concurrent pg_dump session with the privileges of the role running pg_dump (which is often a superuser). The attack involves replacing a sequence or similar object with a view or foreign table that will execute malicious code. To prevent this, introduce a new server parameter restrict_nonsystem_relation_kind that can disable expansion of non-builtin views as well as access to foreign tables, and teach pg_dump to set it when available. Note that the attack is prevented only if both pg_dump and the server it is dumping from are new enough to have this fix. Bug Fixes and Improvements Avoid incorrect results from "Merge Right Anti Join" plans, where if the inner relation is known to have unique join keys, the merge could misbehave when there are duplicated join keys in the outer relation. Prevent infinite loop in VACUUM. Fix partition pruning setup during ALTER TABLE DETACH ... PARTITION CONCURRENTLY. Fix behavior of stable functions that are used as an argument to a CALL statement. pg_sequence_last_value() now returns NULL instead of throwing an error when called on unlogged sequences on standby servers and on temporary sequences of other sessions. Fix parsing of ignored operators in websearch_to_tsquery(). Correctly check updatability of view columns targeted by INSERT ... DEFAULT. Lock owned sequences during ALTER TABLE ... SET LOGGED|UNLOGGED. Don't throw an error if a queued AFTER trigger no longer exists. Fix selection of an arbiter index for INSERT ... ON CONFLICT when the desired index has expressions or predicates, for example, through an updatable view. Refuse to modify a temporary table of another session with ALTER TABLE. Fix handling of extended statistics on expressions in CREATE TABLE ... LIKE STATISTICS. Fix failure to recalculate sub-queries generated from MIN() or MAX() aggregates. Disallow underscores in positional parameters. Avoid crashing when a JIT-inlined backend function throws an error. Fix handling of subtransactions of prepared transactions when starting a hot standby server. Prevent incorrect initialization of logical replication slots. Fix memory leak in the logical replication WAL sender when publishing changes to a partitioned table whose partitions have row types that are physically different from the table. Disable creation of stateful TLS session tickets by OpenSSL. Fix how PL/pgSQL handles integer ranges containing underscores (e.g., FOR i IN 1_001..1_002). Fix incompatibility between PL/Perl and Perl 5.40. Several fixes related to recursive PL/Python functions and triggers. Ensure that pg_restore -l reports dependent table of contents entries correctly. pg_stat_statements now passes a query ID for utility (non-SELECT/INSERT/UPDATE) statements that appears in SQL-language functions. Fix for postgres_fdw when mapping a foreign table to a nontrivial remote view. postgres_fdw no longer sends a FETCH FIRST WITH TIES clause to a remote server.
revbump after icu and protobuf updates
postgresql: updated to 16.1, 15.5, 14.10, 13.13, 12.17, and 11.22 Security Issues CVE-2023-5868: Memory disclosure in aggregate function calls CVE-2023-5869: Buffer overrun from integer overflow in array modification CVE-2023-5870: Role pg_signal_backend can signal certain superuser processes Bug Fixes and Improvements This update fixes over 55 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 16. Some of these issues may also affect other supported versions of PostgreSQL. Fix issue where GiST indexes had an incorrect behavior during a "page split" operation that could lead to incorrect results in subsequent index searches. Please reindex GiST indexes after installing this update. Fix issue where B-tree indexes would incorrectly de-duplicate interval columns. Please reindex any B-tree index that includes an interval column after installing this update. Provide more efficient indexing of date, timestamptz, and timestamp values in BRIN indexes when using a minmax_multi opsclass. While not required, we recommend reindexing BRIN indexes that include these data types after installing this update. Fix for bulk table insertion into partitioned tables. Fix for hash-partitioned tables with multiple partition keys during step generation and runtime pruning that could lead to crashes in some cases. Throw the correct error if pgrowlocks() is applied to a partitioned table Fix inconsistent rechecking of concurrently-updated rows during MERGE when using READ COMMITTED mode. Correctly identify the target table in an inherited UPDATE/DELETE/MERGE even when the parent table is excluded by constraints. Fix over-allocation of a constructed tsvector. Fix ALTER SUBSCRIPTION to apply changes in the run_as_owner option. Several fixes for COPY FROM, Several fixes for handling torn reads with pg_control. Fix "could not find pathkey item to sort" errors occurring while planning aggregate functions with ORDER BY or DISTINCT options. When track_io_timing is enabled, include the time taken by relation extension operations as write time. Track the dependencies of cached CALL statements, and re-plan them when needed. Treat out-of-memory failures as FATAL while reading WAL. Fix pg_dump to dump the new run_as_owner option of subscriptions. Fix pg_restore so that selective restores will include both table-level and column-level ACLs for selected tables. Add logic to pg_upgrade to check for use of obsolete data types abstime, reltime, and tinterval. Fix vacuumdb to have multiple -N switches actually exclude tables in multiple schemas. amcheck will no longer report interrupted page deletion as corruption. Fix btree_gin indexes on interval columns to properly return data when using the < and <= operators.
*: recursive bump for icu 74.1
*: bump for openssl 3
postgresql: updated to 15.3, 14.8, 13.11, 12.15, and 11.20 PostgreSQL 15.3, 14.8, 13.11, 12.15, and 11.20 Security Issues CVE-2023-2454: CREATE SCHEMA ... schema_element defeats protective search_path changes. CVE-2023-2455: Row security policies disregard user ID changes after inlining. Bug Fixes and Improvements This update fixes over 80 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: Several fixes for CREATE DATABASE when using the STRATEGY = WAL_LOG, including a potential corruption that could lose modifications to a template/source database. Fix crash with CREATE SCHEMA AUTHORIZATION. Several fixes for MERGE. Several fixes for triggers in partitioned tables. Disallow altering composite types that are stored in indexes. Ensure that COPY TO from a parent table with row-level security enabled does not copy any rows from child tables. Adjust text-search-related character classification logic to correctly detect whether the prevailing locale is C when the default collation of a database uses the ICU provider. Re-allow exponential notation in ISO-8601 interval fields. Improve error reporting for various invalid JSON string literals. Fix data corruption due to vacuum_defer_cleanup_age being larger than the current 64-bit xid. Several fixes for the query parser and planner, including better detection of improperly-nested aggregates. Fix partition pruning bug with the boolean IS NOT TRUE and IS NOT FALSE conditions. Prior to this, NULL partitions were accidentally pruned. Fix memory leak in memoize plan execution. Fix buffer refcount leak on foreign tables using partitions when performing batched inserts. Restore support for sub-millisecond vacuum_cost_delay settings. Several fixes for views and rules. Avoid unnecessary work while scanning a multi-column BRIN index with multiple scan keys. Ignore dropped columns and generated columns during logical replication of an UPDATE or DELETE action. Several fixes for naming and availability of wait events. Support RSA-PSS certificates with SCRAM-SHA-256 channel binding. This feature requires building with OpenSSL 1.1.1 or newer. Avoid race condition with process ID tracking on Windows. Fix memory leak within a session for PL/pgSQL DO blocks that use cast expressions. Tighten array dimensionality checks from PL/Perl and PL/Python when converting list structures to multi-dimensional SQL arrays. Fix pg_dump so that partitioned tables that are hash-partitioned on an enumerated type column can be restored successfully. Fix for pg_trgm where an unsatisfiable regular expression could lead to a crash when using a GiST or GIN index. Limit memory usage of pg_get_wal_records_info() in pg_walinspect.
revbump after textproc/icu update
postgresql: updated to 15.2, 14.7, 13.10, 12.14, and 11.19 Security Issues CVE-2022-41862: Client memory disclosure when connecting, with Kerberos, to modified server. Versions Affected: 12 - 15. A modified, unauthenticated server or an unauthenticated man-in-the-middle can send an unterminated string during the establishment of Kerberos transport encryption. When a libpq client application has a Kerberos credential cache and doesn't explicitly disable option gssencmode, a server can cause libpq to over-read and report an error message containing uninitialized bytes from and following its receive buffer. If libpq's caller somehow makes that message accessible to the attacker, this achieves a disclosure of the over-read bytes. We have not confirmed or ruled out viability of attacks that arrange for a crash or for presence of notable, confidential information in disclosed bytes. The PostgreSQL project thanks Jacob Champion for reporting this problem. Bug Fixes and Improvements This update fixes over 60 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 partitioned tables to correctly update GENERATED columns in child tables if the GENERATED column does not exist in the parent table or the child generated column has different dependencies than the parent. Several fixes for the MERGE command. Allow a WITH RECURSIVE ... CYCLE query to access its SET output column. Fix an issue with bulk insertions on foreign tables that could lead to logical inconsistencies, for example, a BEFORE ROW trigger may not process rows that should be available. Reject uses of undefined variables in jsonpath existence checks. Fix for jsonb subscripting that come directly from a text column in a table. Honor updated values of checkpoint_completion_target on reload. Log the correct ending timestamp in recovery_target_xid mode. Fix issue to allow column lists longer than 100 when using logical replication. Prevent "wrong tuple length" failure at the end of VACUUM. Avoid an immediate commit after ANALYZE when using query pipelining. Several fixes to the query planner, including one that provides more opportunities for using memoization with partitionwise joins. Fix for statistics collection to correctly handle when a relation changes type (e.g. a table is converted to a view). Ensure full text search queries can be cancelled while performing phrase matches. Fix deadlock between DROP DATABASE and logical replication worker process. Fix small session-lifespan memory leak when CREATE SUBSCRIPTION fails its connection attempt. Performance improvement for replicas with hot_standby enabled that are processing SELECT queries. Several fixes for logical decoding that improve its stability and bloat handling. Fix the default logical replication plug-in, pgoutput, to not send columns that are not listed in a table's replication column list. Fix possible corruption of very large tablespace map files in pg_basebackup. Remove a harmless warning from pg_dump in --if-exists mode when the public schema has a non-default owner. Fix the psql commands \sf and \ef to handle SQL-language functions that have SQL-standard function bodies (i.e. BEGIN ATOMIC). Fix tab completion of ALTER FUNCTION/PROCEDURE/ROUTINE ... SET SCHEMA. Update the pageinspect extension to mark its disk-accessing functions as PARALLEL RESTRICTED. Fix the seg extension to not crash or print garbage if an input number has more than 127 digits.
massive revision bump after textproc/icu update
postgresql15: added version 15.0 PostgreSQL 15 contains many new features and enhancements, including: Support for the SQL MERGE command. Selective publication of tables' contents within logical replication publications, through the ability to specify column lists and row filter conditions. More options for compression, including support for Zstandard (zstd) compression. This includes support for performing compression on the server side during pg_basebackup. Support for structured server log output using the JSON format. Performance improvements, particularly for in-memory and on-disk sorting.