Up to [cvs.NetBSD.org] / pkgsrc / databases / postgresql15-client
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
postgresql1[4-8]: updated to 18.7, 17.12, 16.16, 15.20, 14.25 18.7, 17.12, 16.16, 15.20, 14.25 Security Issues The following security vulnerabilities are closed in this update release. You can find more details about the vulnerabilities and their affected versions in the links below: CVE-2026-6460: Type confusion after ALTER ... SET DATA TYPE executes arbitrary code (CVSS v3.1: 8.8) CVE-2026-6467: Extension script schema mishandling executes arbitrary SQL (CVSS v3.1: 7.2) CVE-2026-14661: dblink and subscriptions can append to arbitrary files (CVSS v3.1: 8.1) CVE-2026-16237: INSERT ... ON CONFLICT can read or modify rows despite auto-updatable view WHERE condition (CVSS v3.1: 5.4) CVE-2026-16240: pg_basebackup can use backup manifest content as a format string (CVSS v3.1: 3.7) CVE-2026-18447: Output parameter type confusion executes arbitrary code (CVSS v3.1: 8.8) CVE-2026-116303: Foreign key and JSON conversions bypass EXECUTE privilege on cast functions (CVSS v3.1: 3.1) CVE-2026-116304: Parallel RECORD typmod use-after-free executes arbitrary code (CVSS v3.1: 8.8) CVE-2026-116306: Composite-type change during field assignment executes arbitrary code (CVSS v3.1: 8.8) CVE-2026-116307: plperl prepared-query use-after-free executes arbitrary code (CVSS v3.1: 8.8) CVE-2026-116308: dict_int reads beyond zero-length tokens (CVSS v3.1: 4.3) CVE-2026-116309: plperl blessed-reference type confusion may execute arbitrary code (CVSS v3.1: 8.8) CVE-2026-116310: COPY error context uses freed field storage (CVSS v3.1: 4.3) CVE-2026-116311: DROP OWNED can remove restrictive row security policies from non-owned tables (CVSS v3.1: 5.4) CVE-2026-116312: MERGE can place the wrong row in a trigger transition table (CVSS v3.1: 5.4) CVE-2026-116313: vacuumdb --missing-stats-only lets a database owner execute code as the vacuumdb user (CVSS v3.1: 7.2) CVE-2026-116314: pg_restore executes arbitrary code due to missing non-plain archive validation (CVSS v3.1: 8.8) CVE-2026-116315: tsvector_delete() heap buffer overflow executes arbitrary code (CVSS v3.1: 8.8) CVE-2026-116316: Security-restricted operations can create types in pg_temp, which later queries of the session find (CVSS v3.1: 8.8) CVE-2026-116317: ts_rank_cd() heap buffer overflow may execute arbitrary code (CVSS v3.1: 8.8) CVE-2026-116318: pg_dump not-null constraint name allows SQL injection (CVSS v3.1: 8.8) CVE-2026-116319: plperl reentrant return_next() use-after-free executes arbitrary code (CVSS v3.1: 8.8) CVE-2026-116320: plperl array and hash conversion use-after-free executes arbitrary code (CVSS v3.1: 8.8) CVE-2026-116321: Unterminated name value discloses server memory (CVSS v3.1: 4.3) CVE-2026-116322: Pre-authentication cancel request can leak a spinlock (CVSS v3.1: 5.3) CVE-2026-116323: pltcl reentrant result conversion use-after-free executes arbitrary code (CVSS v3.1: 8.8) CVE-2026-116325: reindexdb index name quoting allows SQL injection (CVSS v3.1: 8) CVE-2026-116326: plperl tied-object exceptions follow stale sigjmp_buf (CVSS v3.1: 8.8) CVE-2026-116327: security_barrier analysis can expose hidden values through indirect expressions (CVSS v3.1: 4.3) CVE-2026-116328: Generation memory context integer wraparound executes arbitrary code (CVSS v3.1: 8.8) CVE-2026-116329: Statistics import type confusion executes arbitrary code (CVSS v3.1: 8.8) CVE-2026-116330: pg_dump tar restore.sql fails to block psql command injection (CVSS v3.1: 8.8) CVE-2026-116331: Min/max aggregate type confusion executes arbitrary code (CVSS v3.1: 8.8) CVE-2026-116332: Portal setup use-after-free executes arbitrary code (CVSS v3.1: 8.8) CVE-2026-116333: Parallel B-tree array scan reads beyond array bounds (CVSS v3.1: 6.5) CVE-2026-116335: Commutator or negator result-type confusion executes arbitrary code (CVSS v3.1: 8.8) CVE-2026-116336: REINDEX CONCURRENTLY does not block DROP INDEX during index functions (CVSS v3.1: 8.8) CVE-2026-120139: Tuple-size integer wraparound executes arbitrary code (CVSS v3.1: 8.8) CVE-2026-120141: Materialized set-returning function type confusion executes arbitrary code (CVSS v3.1: 8.8) CVE-2026-120142: Dropped-column type confusion executes arbitrary code (CVSS v3.1: 8.8) CVE-2026-120143: Transition-table cursor use-after-free executes arbitrary code (CVSS v3.1: 8.8) CVE-2026-120144: Type-cache invalidation gap executes arbitrary code (CVSS v3.1: 8.8) CVE-2026-120145: Logical replication can write to subscriber system catalogs, executing arbitrary code (CVSS v3.1: 8.8) CVE-2026-120146: REASSIGN OWNED bypasses role SET and CREATEDB checks (CVSS v3.1: 4.3) CVE-2026-120147: dblink reentrant disconnect use-after-free executes arbitrary code (CVSS v3.1: 8.8) CVE-2026-120148: Extended-statistics pseudo-type confusion executes arbitrary code (CVSS v3.1: 8.1) CVE-2026-120149: FDW batch-insert mismatch executes arbitrary code (CVSS v3.1: 8.8) CVE-2026-120150: Expanded-record domain-check use-after-free executes arbitrary code (CVSS v3.1: 8.8) CVE-2026-120151: plpgsql record-field type confusion executes arbitrary code (CVSS v3.1: 8.8) CVE-2026-120152: pg_show_all_settings() use-after-free discloses memory (CVSS v3.1: 4.3) CVE-2026-120153: Extension-script substitutions allow SQL injection through object names (CVSS v3.1: 7.2) CVE-2026-120154: INSERT ... ON CONFLICT can read rows despite row security policies (CVSS v3.1: 4.3) Bug Fixes and Improvements This update fixes over 140 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 18. Many of these issues also affect other supported versions of PostgreSQL. Fix exporting and importing snapshots taken on a standby server. The issue was detected when running a parallel pg_dump against a standby server, and could corrupt both the dump output and the standby server's data. More generally, a transaction that imported a snapshot taken on a standby server could return wrong results. Several fixes for GIN indexes that could lead to index corruption, causing queries to miss rows or to return unrelated rows. If you suspect a GIN index is affected, you should reindex it. See the release notes for more details on the issue, and the "Updating" section for post-update steps. Fix possible index corruption in pg_trgm GiST indexes that could cause searches to miss matching rows. You need to reindex after updating; see the "Updating" section. Fix a case where, after REINDEX CONCURRENTLY rebuilt an index on a TOAST table, later index updates could be missed, leading to missing chunk number errors. If you've encountered this issue, after updating, you'll need to reindex. See the "Updating" section. Disallow NOT NULL NO INHERIT constraints on partitioned tables in all cases, including CREATE TABLE ... LIKE. Previously, this could allow a partition to contain NULL values when it should not. See the "Updating" section for how to find and repair affected constraints. Disable B-tree index deduplication for columns declared as bpchar without a length, which could cause index-only scans to return wrong results. If you have B-tree indexes on bpchar columns, you should reindex them after updating. See the "Updating" section. Several fixes for incremental backups that could produce corrupt backups. We recommend taking a new full backup after updating and using it for subsequent incremental backups. See the "Updating" section. Several fixes for base backups, including avoiding a torn copy of the pg_control file, and avoiding truncated or zero-padded copies of files such as postgresql.auto.conf that are replaced while the backup is running. Rework the planner's join removal implementation. While this is a significant change for an update release, it was made to avoid continued bugs from the previous implementation. Fix possible loss of rows during a table rewrite (for example, CLUSTER or VACUUM FULL) when a row had been updated by a subtransaction that later aborted. Fix parallel vacuum I/O timing reports. Several fixes that could cause data loss or inconsistency after a crash, including starting a checkpoint while creating a multixact or while aborting a prepared transaction. This release also writes the state files of pending prepared transactions atomically, as a crash could previously leave behind an invalid file that prevented the server from starting. Several fixes to the planner that could produce wrong query results, including queries with LATERAL references, outer joins, self-join elimination on tables using inheritance, DISTINCT ON in a subquery with set-returning functions, and queries using non-deterministic collations. Several fixes to partition pruning that could cause rows to be missed, including multi-column RANGE-partitioned tables when a query filters only on the leading columns, DEFAULT partitions on tables using MINVALUE or MAXVALUE bounds, and concurrent updates that could silently skip rows that should be updated. Fix INSERT ... ON CONFLICT to acquire a predicate lock on the conflicting row under SERIALIZABLE isolation. Previously, concurrent updates that should have failed with a serialization error could succeed. Fix MERGE with WHEN NOT MATCHED BY SOURCE when the target row is concurrently deleted. Previously, a WHEN NOT MATCHED BY TARGET action could run instead, giving incorrect results. Several fixes for SQL/JSON functions such as JSON_TABLE and JSON_VALUE that could return incorrect results. Several fixes for logical replication that could cause a subscriber to apply changes incorrectly. Several fixes for standby servers, including avoiding unnecessary replay delays and query cancellations in certain cases. Fix psql to accept multiple COPY ... FROM STDIN commands in a single command string. The fix for CVE-2026-6464 caused psql to reject these. Several fixes that could cause a dump to fail to restore, or cause a restored view to behave differently from the original. These include views and rules that use AT TIME ZONE in a FROM clause or a target alias named set, tsvector and tsquery values that could fail to reload. Fix the server becoming stuck, instead of exiting, if the startup process crashes while the server is restarting after a crash.
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.
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
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.
postgresql1[0-5]: Updated to 15.1, 14.6, 13.9, 12.13, 11.18, and 10.23 PostgreSQL 15.1, 14.6, 13.9, 12.13, 11.18, and 10.23 Released! Bug Fixes and Improvements This update fixes over 25 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 updatable views for INSERT statements that include multi-row VALUES clauses with a DEFAULT set. Disallow rules named _RETURN that are not ON SELECT rules. Disallow use of MERGE on a partitioned table that has foreign-table partitions. Fix for construction of per-partition foreign key constraints while doing ALTER TABLE ... ATTACH PARTITION, where previously incorrect or duplicate constraints could be built. Fix for a planner failure with extended statistics on partitioned or inherited tables. Fix bugs in logical decoding that could lead to memory leaks when replay starts from a point between the beginning of a transaction and the beginning of its subtransaction. Fix issues with slow shutdown of replication workers by allowing interrupts in more places. Disallow logical replication into foreign-table partitions. Prevent crash in replication works after a SQL or PL/pgSQL function syntax error. psql -c now exits with a nonzero status if the query is canceled. Allow cross-platform tablespace relocation in pg_basebackup. Fix pg_dump to include comments attached to some CHECK constraints.
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.