Up to [cvs.NetBSD.org] / pkgsrc / databases / postgresql14-plpython
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.
postgresql1*: updated to 16.2, 15.6, 14.11, 13.14, 12.18 Security Issues CVE-2024-0985: PostgreSQL non-owner REFRESH MATERIALIZED VIEW CONCURRENTLY executes arbitrary SQL Bug Fixes and Improvements This update fixes over 65 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 memory leak when performing JIT inlining that could lead to out-of-memory conditions. Several query planner fixes. Align MERGE behavior with UPDATE when updating a partition key column and skip firing AFTER UPDATE ROW trigger and other post-update actions. Fix problems with duplicate token names in ALTER TEXT SEARCH CONFIGURATION ... MAPPING commands. Fix DROP ROLE with duplicate role names. Properly lock the associated table during DROP STATISTICS to prevent errors if ANALYZE is running concurrently. Fix function volatility checking for GENERATED and DEFAULT expressions. Ensure collation matches when matching an existing index to a new partitioned index. Avoid failure if a child index is dropped concurrently with REINDEX INDEX on a partitioned index. Fix for locking during cleanup of GIN indexes. For this case, if multiple processes tried to clean the same GIN index page, there was a chance of index corruption. If you believe you were affected by this issue, reindex your GIN indexes after installing this update. Avoid failure with partitioned SP-GiST indexes. Several ownership fixes for large objects. In EXPLAIN (BUFFERS), change name of I/O timing data "shared/local" to "shared". Ensure durability of the CREATE DATABASE command if a system crash occurred during or shortly after execution. Add more logging messages when starting and ending recovery from a backup. Revert a change that made the walreceiver process unresponsive to SIGTERM while waiting for a replication connection to be established. Several fixes for logical replication. Fix incompatibility with OpenSSL 3.2. Fix PL/pgSQL to allow CREATE FUNCTION/CREATE PROCEDURE SQL commands that use SQL-standard function bodies. Fix for error handling in libpq pipeline mode. Ensure initdb always uncomments postgresql.conf entries for the lc_ family of parameters. In pg_dump, don't dump RLS policies or security labels for extension member objects.
postgresql14: added version 14.0 PostgreSQL 14 contains many new features and enhancements, including: Stored procedures can now return data via OUT parameters. The SQL-standard SEARCH and CYCLE options for common table expressions have been implemented. Subscripting can now be applied to any data type for which it is a useful notation, not only arrays. In this release, the jsonb and hstore types have gained subscripting operators. Range types have been extended by adding multiranges, allowing representation of noncontiguous data ranges. Numerous performance improvements have been made for parallel queries, heavily-concurrent workloads, partitioned tables, logical replication, and vacuuming. B-tree index updates are managed more efficiently, reducing index bloat. VACUUM automatically becomes more aggressive, and skips inessential cleanup, if the database starts to approach a transaction ID wraparound condition. Extended statistics can now be collected on expressions, allowing better planning results for complex queries. libpq now has the ability to pipeline multiple queries, which can boost throughput over high-latency connections.