![[BACK]](/icons/back.gif){kind=icon}
Up to [cvs.NetBSD.org] / pkgsrc / databases / postgresql12
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
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 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.
postgresql: updated to 16.3, 15.7, 14.12, 13.15, 12.19 PostgreSQL 16.3, 15.7, 14.12, 13.15, and 12.19 The PostgreSQL Global Development Group has released an update to all supported versions of PostgreSQL, including 16.3, 15.7, 14.12, 13.15, and 12.19. This release fixes one security vulnerability and over 55 bugs reported over the last several months. A security vulnerability was found in the system views pg_stats_ext and pg_stats_ext_exprs, potentially allowing authenticated database users to see data they don't have sufficient privileges to view. The fix for this vulnerability only fixes fresh PostgreSQL installations, namely those that are created with the initdb utility after this fix is applied. If you have a current PostgreSQL installation and are concerned about this issue, please follow the instructions in the "Updating" section for remediation steps. For the full list of changes, please review the release notes.
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.
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.
postgresql: updated to 15.4, 14.9, 13.12, 12.16, 11.21 PostgreSQL 15.4, 14.9, 13.12, 12.16, 11.21 This release fixes two security vulnerabilities and over 40 bugs reported over the last several months. Security Issues CVE-2023-39417: Extension script @substitutions@ within quoting allow SQL injection. CVE-2023-39418: MERGE fails to enforce UPDATE or SELECT row security policies.
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.
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.
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.
postgresql: updated to 14.5, 13.8, 12.12, 11.17, 10.22 This update fixes over 40 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 14. Some of these issues may also affect other supported versions of PostgreSQL. Included in this release: Fix replay of CREATE DATABASE write-ahead log (WAL) records on standby servers when encountering a missing tablespace directory. Add support for tablespaces that are plain directories instead of symbolic links to other directories. Fix permission checks in CREATE INDEX to use the user's permissions. This fixes broken dump/restore scenarios that relied on the behavior prior to the fix for CVE-2022-1552. In the extended query protocol, force an immediate commit after CREATE DATABASE and other commands that can't run in a transaction block. Fix a race condition around checking transaction visibility that was more likely to happen when using synchronous replication. Fix incorrect permission-checking code for extended statistics. Fix extended statistics machinery to handle most common value (MCV)-type statistics on boolean-valued expressions. Avoid planner core dump with constant = ANY(array) clauses when there are MCV-type extended statistics on the array variable. Allow cancellation of ANALYZE while it is computing extended statistics. Fix ALTER TABLE ... ENABLE/DISABLE TRIGGER to handle recursion for triggers on partitioned tables. Reject ROW() expressions and functions in FROM that have more than 1600 columns. Fix memory leak in logical replication subscribers. Fix checks in logical replication of replica identity when the target table is partitioned. Arrange to clean up after commit-time errors within SPI_commit(), rather than expecting callers to do that. This includes a fix for the same scenario in PL/Python, which had reported crashes on Python 3.11 and memory leaks on older versions of Python 3. Improve handling in libpq of idle states in pipeline mode. In the psql \watch command, echo a newline after cancellation with control-C. Fix pg_upgrade to detect non-upgradable usages of functions accepting anyarray parameters. Several postgres_fdw fixes, including prevention of batch insertions when there are WITH CHECK OPTION constraints present.
postgresqlNN: updated to 14.3, 13.7, 12.11, 11.16, and 10.21 The PostgreSQL Global Development Group has released an update to all supported versions of PostgreSQL, including 14.3, 13.7, 12.11, 11.16, and 10.21. This release closes one security vulnerability and fixes over 50 bugs reported over the last three months. CVE-2022-1552: Autovacuum, REINDEX, and others omit "security restricted operation" sandbox. Versions Affected: 10 - 14. The security team typically does not test unsupported versions, but this problem is quite old. Autovacuum, REINDEX, CREATE INDEX, REFRESH MATERIALIZED VIEW, CLUSTER, and pg_amcheck made incomplete efforts to operate safely when a privileged user is maintaining another user's objects. Those commands activated relevant protections too late or not at all. An attacker having permission to create non-temp objects in at least one schema could execute arbitrary SQL functions under a superuser identity. While promptly updating PostgreSQL is the best remediation for most users, a user unable to do that can work around the vulnerability by disabling autovacuum, not manually running the above commands, and not restoring from output of the pg_dump command. Performance may degrade quickly under this workaround. VACUUM is safe, and all commands are fine when a trusted user owns the target object. Bug Fixes and Improvements This update fixes over 50 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 14. Some of these issues may also affect other supported versions of PostgreSQL. Included in this release: Fix issue that could lead to corruption of GiST indexes on ltree columns. After upgrading, you will need to reindex any GiST indexes on ltree columns. Column names in tuples produced by a whole-row variable (e.g. tbl.*) outside of a top-level of a SELECT list are now always associated with those of the associated named composite type, if there is one. The release notes detail a workaround if you depend on the previous behavior. Fix incorrect rounding when extracting epoch values from interval types. Prevent issues with calling pg_stat_get_replication_slot(NULL). Fix incorrect output for types timestamptz and timetz in table_to_xmlschema(). Fix errors related to a planner issue that affected asynchronous remote queries. Fix planner failure if a query using SEARCH or CYCLE features contains a duplicate common-table expression (WITH) name. Fix ALTER FUNCTION to support changing a function's parallelism property and its SET-variable list in the same command. Fix incorrect sorting of table rows when using CLUSTER on an index whose leading key is an expression. Prevent data loss if a system crash occurs shortly after a sorted GiST index build. Fix risk of deadlock failures while dropping a partitioned index. Fix race condition between DROP TABLESPACE and checkpointing that could fail to remove all dead files from the tablespace directory. Fix potential issue in crash recovery after a TRUNCATE command that overlaps with a checkpoint. Re-allow _ as the first character in a custom configuration parameter name. Fix PANIC: xlog flush request is not satisfied failure during standby promotion when there is a missing WAL continuation record. Fix possibility of self-deadlock in hot standby conflict handling. Ensure that logical replication apply workers can be restarted when the server is near the max_sync_workers_per_subscription limit. Disallow execution of SPI functions during PL/Perl function compilation. libpq now accepts root-owned SSL private key files, which matches the rules the server has used since the 9.6 release. Re-allow database.schema.table patterns in psql, pg_dump, and pg_amcheck. Several fixes for pageinspect to improve overall stability. Disable batch insertion in postgres_fdw when BEFORE INSERT ... FOR EACH ROW triggers exist on the foreign table. Update JIT code to work with LLVM 14.
postgresql1N: updated to 14.2, 13.6, 12.10, 11.15, and 10.20 PostgreSQL 14.2, 13.6, 12.10, 11.15, and 10.20 Released! This update fixes over 55 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 14. Some of these issues may also affect other supported versions of PostgreSQL. Included in this release: Fix for a low probability scenario of index corruption when a HOT (heap-only tuple) chain changes state during VACUUM. Encountering this issue is unlikely, but if you are concerned, please consider reindexing. Fix for using REINDEX CONCURRENTLY on TOAST table indexes to prevent corruption. You can fix any TOAST indexes by reindexing them again. The psql \password command now defaults to setting the password for the role defined by CURRENT_USER. Additionally, the role name is now included in the password prompt. Build extended statistics for partitioned tables. If you previously added extended statistics to a partitioned table, you should run ANALYZE on those tables. As autovacuum currently does not process partitioned tables, you must periodically run ANALYZE on any partitioned tables to update their statistics. Fix crash with ALTER STATISTICS when the statistics object is dropped concurrently. Fix crash with multiranges when extracting variable-length data types. Several fixes to the query planner that lead to incorrect query results. Several fixes for query plan memoization. Fix startup of a physical replica to tolerate transaction ID wraparound. When using logical replication, avoid duplicate transmission of a partitioned table's data when the publication includes both the child and parent tables. Disallow altering data type of a partitioned table's columns when the partitioned table's row type is used as a composite type elsewhere. Disallow ALTER TABLE ... DROP NOT NULL for a column that is part of a replica identity index. Several fixes for caching that correct logical replication behavior and improve performance. Fix memory leak when updating expression indexes. Avoid leaking memory during REASSIGN OWNED BY operations that reassign ownership of many objects. Fix display of whole-row variables appearing in INSERT ... VALUES rules. Fix race condition that could lead to failure to localize error messages that are reported early in multi-threaded use of libpq or ecpglib. Fix psql \d command for identifying parent triggers. Fix failures on Windows when using the terminal as data source or destination. This affected the psql \copy command and using pg_recvlogical with -f -. Fix the pg_dump --inserts and --column-inserts modes to handle tables that contain both generated and dropped columns. Fix edge cases in how postgres_fdw handles asynchronous queries. These errors could lead to crashes or incorrect results when attempting to run parallel scans of foreign tables. For the full list of changes available, please review the release notes.
Pullup ticket #6535 - requested by bsiegert
databases/postgresql: security fix
Revisions pulled up:
- databases/postgresql10-docs/PLIST 1.20
- databases/postgresql10-server/PLIST 1.10
- databases/postgresql10/Makefile 1.27
- databases/postgresql10/Makefile.common 1.31
- databases/postgresql10/distinfo 1.25
- databases/postgresql11-docs/PLIST 1.15
- databases/postgresql11-server/PLIST 1.5
- databases/postgresql11/Makefile.common 1.24
- databases/postgresql11/distinfo 1.20
- databases/postgresql12-docs/PLIST 1.10
- databases/postgresql12-server/PLIST 1.6
- databases/postgresql12/Makefile 1.18
- databases/postgresql12/Makefile.common 1.17
- databases/postgresql12/distinfo 1.14
- databases/postgresql13-client/PLIST 1.5
- databases/postgresql13-docs/PLIST 1.6
- databases/postgresql13-server/PLIST 1.4
- databases/postgresql13/Makefile 1.9
- databases/postgresql13/Makefile.common 1.10
- databases/postgresql13/distinfo 1.10
- databases/postgresql96-docs/PLIST 1.24
- databases/postgresql96-server/PLIST 1.9
- databases/postgresql96/Makefile 1.16
- databases/postgresql96/Makefile.common 1.36
- databases/postgresql96/distinfo 1.29
---
Module Name: pkgsrc
Committed By: adam
Date: Tue Nov 16 10:14:39 UTC 2021
Modified Files:
pkgsrc/databases/postgresql10: Makefile.common distinfo
pkgsrc/databases/postgresql10-docs: PLIST
pkgsrc/databases/postgresql10-server: PLIST
pkgsrc/databases/postgresql11: Makefile.common distinfo
pkgsrc/databases/postgresql11-docs: PLIST
pkgsrc/databases/postgresql11-server: PLIST
pkgsrc/databases/postgresql12: Makefile.common distinfo
pkgsrc/databases/postgresql12-docs: PLIST
pkgsrc/databases/postgresql12-server: PLIST
pkgsrc/databases/postgresql13: Makefile.common distinfo
pkgsrc/databases/postgresql13-client: PLIST
pkgsrc/databases/postgresql13-docs: PLIST
pkgsrc/databases/postgresql13-server: PLIST
pkgsrc/databases/postgresql96: Makefile.common distinfo
pkgsrc/databases/postgresql96-docs: PLIST
pkgsrc/databases/postgresql96-server: PLIST
Log Message:
postgresql: updated to 13.5, 12.9, 11.14, 10.19, 9.6.24
PostgreSQL 13.5, 12.9, 11.14, 10.19, and 9.6.24
Security Issues
CVE-2021-23214: Server processes unencrypted bytes from man-in-the-middle
Versions Affected: 9.6 - 14. The security team typically does not test
unsupported versions, but this problem is quite old.
When the server is configured to use trust authentication with a
clientcert requirement or to use cert authentication, a
man-in-the-middle attacker can inject arbitrary SQL queries when a
connection is first established, despite the use of SSL certificate
verification and encryption.
The PostgreSQL project thanks Jacob Champion for reporting this problem.
CVE-2021-23222: libpq processes unencrypted bytes from man-in-the-middle
Versions Affected: 9.6 - 14. The security team typically does not test
unsupported versions, but this problem is quite old.
A man-in-the-middle attacker can inject false responses to the
client's first few queries, despite the use of SSL certificate
verification and encryption.
If more preconditions hold, the attacker can exfiltrate the client's
password or other confidential data that might be transmitted early in
a session. The attacker must have a way to trick the client's intended
server into making the confidential data accessible to the attacker. A
known implementation having that property is a PostgreSQL
configuration vulnerable to CVE-2021-23214.
As with any exploitation of CVE-2021-23214, the server must be using
trust authentication with a clientcert requirement or using cert
authentication. To disclose a password, the client must be in
possession of a password, which is atypical when using an
authentication configuration vulnerable to CVE-2021-23214. The
attacker must have some other way to access the server to retrieve the
exfiltrated data (a valid, unprivileged login account would be
sufficient).
The PostgreSQL project thanks Jacob Champion for reporting this problem.
Bug Fixes and Improvements
This update fixes over 40 bugs that were reported in the last several
months. The issues listed below affect PostgreSQL 14. Some of these
issues may also affect other supported versions of PostgreSQL.
Some of these fixes include:
Fix physical replication for cases where the primary crashes after
shipping a WAL segment that ends with a partial WAL record. When
applying this update, update your standby servers before the primary
so that they will be ready to handle the fix if the primary happens to
crash.
Fix parallel VACUUM so that it will process indexes below the
min_parallel_index_scan_size threshold if the table has at least two
indexes that are above that size. This problem does not affect
autovacuum. If you are affected by this issue, you should reindex any
manually-vacuumed tables.
Fix causes of CREATE INDEX CONCURRENTLY and REINDEX CONCURRENTLY
writing corrupt indexes. You should reindex any concurrently-built
indexes.
Fix for attaching/detaching a partition that could allow certain
INSERT/UPDATE queries to misbehave in active sessions.
Fix for creating a new range type with CREATE TYPE that could cause
problems for later event triggers or subsequent executions of the
CREATE TYPE command.
Fix updates of element fields in arrays of a domain that is a part of
a composite.
Disallow the combination of FETCH FIRST WITH TIES and FOR UPDATE SKIP LOCKED.
Fix corner-case loss of precision in the numeric power() function.
Fix restoration of a Portal's snapshot inside a subtransaction, which
could lead to a crash. For example, this could occur in PL/pgSQL when
a COMMIT is immediately followed by a BEGIN ... EXCEPTION block that
performs a query.
Clean up correctly if a transaction fails after exporting its
snapshot. This could occur if a replication slot was created then
rolled back, and then another replication slot was created in the same
session.
Fix for "overflowed-subtransaction" wraparound tracking on standby
servers that could lead to performance degradation.
Ensure that prepared transactions are properly accounted for during
promotion of a standby server.
Ensure that the correct lock level is used when renaming a table.
Avoid crash when dropping a role that owns objects being dropped concurrently.
Disallow setting huge_pages to on when shared_memory_type is sysv
Fix query type checking in the PL/pgSQL RETURN QUERY.
Several fixes for pg_dump, including the ability to dump non-global
default privileges correctly.
Use the CLDR project's data to map Windows time zone names to IANA time zones.
This update also contains tzdata release 2021e for DST law changes in
Fiji, Jordan, Palestine, and Samoa, plus historical corrections for
Barbados, Cook Islands, Guyana, Niue, Portugal, and Tonga.
Also, the Pacific/Enderbury zone has been renamed to Pacific/Kanton.
Also, the following zones have been merged into nearby, more-populous
zones whose clocks have agreed with them since 1970: Africa/Accra,
America/Atikokan, America/Blanc-Sablon, America/Creston,
America/Curacao, America/Nassau, America/Port_of_Spain,
Antarctica/DumontDUrville, and Antarctica/Syowa. In all these cases,
the previous zone name remains as an alias.
---
Module Name: pkgsrc
Committed By: adam
Date: Tue Nov 16 10:17:40 UTC 2021
Modified Files:
pkgsrc/databases/postgresql10: Makefile
pkgsrc/databases/postgresql12: Makefile
pkgsrc/databases/postgresql13: Makefile
pkgsrc/databases/postgresql96: Makefile
Log Message:
postgresqlNN: reset revision
postgresql: updated to 14.1, 13.5, 12.9, 11.14, 10.19, 9.6.24 PostgreSQL 14.1, 13.5, 12.9, 11.14, 10.19, and 9.6.24 Security Issues CVE-2021-23214: Server processes unencrypted bytes from man-in-the-middle Versions Affected: 9.6 - 14. The security team typically does not test unsupported versions, but this problem is quite old. When the server is configured to use trust authentication with a clientcert requirement or to use cert authentication, a man-in-the-middle attacker can inject arbitrary SQL queries when a connection is first established, despite the use of SSL certificate verification and encryption. The PostgreSQL project thanks Jacob Champion for reporting this problem. CVE-2021-23222: libpq processes unencrypted bytes from man-in-the-middle Versions Affected: 9.6 - 14. The security team typically does not test unsupported versions, but this problem is quite old. A man-in-the-middle attacker can inject false responses to the client's first few queries, despite the use of SSL certificate verification and encryption. If more preconditions hold, the attacker can exfiltrate the client's password or other confidential data that might be transmitted early in a session. The attacker must have a way to trick the client's intended server into making the confidential data accessible to the attacker. A known implementation having that property is a PostgreSQL configuration vulnerable to CVE-2021-23214. As with any exploitation of CVE-2021-23214, the server must be using trust authentication with a clientcert requirement or using cert authentication. To disclose a password, the client must be in possession of a password, which is atypical when using an authentication configuration vulnerable to CVE-2021-23214. The attacker must have some other way to access the server to retrieve the exfiltrated data (a valid, unprivileged login account would be sufficient). The PostgreSQL project thanks Jacob Champion for reporting this problem. Bug Fixes and Improvements This update fixes over 40 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 14. Some of these issues may also affect other supported versions of PostgreSQL. Some of these fixes include: Fix physical replication for cases where the primary crashes after shipping a WAL segment that ends with a partial WAL record. When applying this update, update your standby servers before the primary so that they will be ready to handle the fix if the primary happens to crash. Fix parallel VACUUM so that it will process indexes below the min_parallel_index_scan_size threshold if the table has at least two indexes that are above that size. This problem does not affect autovacuum. If you are affected by this issue, you should reindex any manually-vacuumed tables. Fix causes of CREATE INDEX CONCURRENTLY and REINDEX CONCURRENTLY writing corrupt indexes. You should reindex any concurrently-built indexes. Fix for attaching/detaching a partition that could allow certain INSERT/UPDATE queries to misbehave in active sessions. Fix for creating a new range type with CREATE TYPE that could cause problems for later event triggers or subsequent executions of the CREATE TYPE command. Fix updates of element fields in arrays of a domain that is a part of a composite. Disallow the combination of FETCH FIRST WITH TIES and FOR UPDATE SKIP LOCKED. Fix corner-case loss of precision in the numeric power() function. Fix restoration of a Portal's snapshot inside a subtransaction, which could lead to a crash. For example, this could occur in PL/pgSQL when a COMMIT is immediately followed by a BEGIN ... EXCEPTION block that performs a query. Clean up correctly if a transaction fails after exporting its snapshot. This could occur if a replication slot was created then rolled back, and then another replication slot was created in the same session. Fix for "overflowed-subtransaction" wraparound tracking on standby servers that could lead to performance degradation. Ensure that prepared transactions are properly accounted for during promotion of a standby server. Ensure that the correct lock level is used when renaming a table. Avoid crash when dropping a role that owns objects being dropped concurrently. Disallow setting huge_pages to on when shared_memory_type is sysv Fix query type checking in the PL/pgSQL RETURN QUERY. Several fixes for pg_dump, including the ability to dump non-global default privileges correctly. Use the CLDR project's data to map Windows time zone names to IANA time zones. This update also contains tzdata release 2021e for DST law changes in Fiji, Jordan, Palestine, and Samoa, plus historical corrections for Barbados, Cook Islands, Guyana, Niue, Portugal, and Tonga. Also, the Pacific/Enderbury zone has been renamed to Pacific/Kanton. Also, the following zones have been merged into nearby, more-populous zones whose clocks have agreed with them since 1970: Africa/Accra, America/Atikokan, America/Blanc-Sablon, America/Creston, America/Curacao, America/Nassau, America/Port_of_Spain, Antarctica/DumontDUrville, and Antarctica/Syowa. In all these cases, the previous zone name remains as an alias.
databases: Replace RMD160 checksums with BLAKE2s checksums All checksums have been double-checked against existing RMD160 and SHA512 hashes The following distfiles could not be fetched (some may be only fetched conditionally): ./databases/cstore/distinfo D6.data.ros.gz ./databases/cstore/distinfo cstore0.2.tar.gz ./databases/cstore/distinfo data4.tar.gz
databases: Remove SHA1 distfile hashes
postgresql: updated to 13.4, 12.8, 11.13, 10.18, 9.6.23 PostgreSQL 13.4, 12.8, 11.13, 10.18, 9.6.23 Security Issues CVE-2021-3677: Memory disclosure in certain queries Versions Affected: 11 - 13. A purpose-crafted query can read arbitrary bytes of server memory. In the default configuration, any authenticated database user can complete this attack at will. The attack does not require the ability to create objects. If server settings include max_worker_processes=0, the known versions of this attack are infeasible. However, undiscovered variants of the attack may be independent of that setting. Bug Fixes and Improvements This update also fixes over 75 bugs that were reported in the last several months. Some of these issues affect only version 13, but many affect all supported versions. Some of these fixes include: Completely disable TLS/SSL renegotiation. This was previously disabled, but the server would still execute a client-initiated renegotiation request. Restore the Portal-level snapshot after COMMIT or ROLLBACK within a procedure. This change fixes cases where an attempt to fetch a toasted value immediately after COMMIT/ROLLBACK would fail with errors like "no known snapshots" or "missing chunk number 0 for toast value". Avoid misbehavior when persisting the output of a cursor that's reading a volatile query. Reject cases where a query in WITH rewrites to just NOTIFY, which would cause a crash. Several corner-case fixes for numeric types. ALTER EXTENSION now locks the extension when adding or removing a member object. The "enabled" status is now copied when a partitioned table's triggers are cloned to a new partition. Avoid alias conflicts in queries generated for REFRESH MATERIALIZED VIEW CONCURRENTLY. This command failed on materialized views containing columns with certain names, notably mv and newdata. Disallow whole-row variables in GENERATED expressions. Several fixes for DROP OWNED BY behavior in relation to row-level security (RLS) policies. Re-allow old-style Windows locale names in CREATE COLLATION commands. walsenders now show their latest replication command in pg_stat_activity, instead of just showing the latest SQL command. pg_settings.pending_restart now shows as true when a pertinent entry in postgresql.conf is removed. On 64-bit Windows, allow the effective value of work_mem * hash_mem_multiplier to exceed 2GB. Update minimum recovery point when WAL replay of a transaction abort record causes file truncation. Advance oldest-required-WAL-segment horizon properly after a replication slot is invalidated. This fixes an issue where the server's WAL storage could run out of space. Improve progress reporting for the sort phase of a parallel B-tree index build. Fix assorted crash cases in logical replication of partitioned-table updates and when firing AFTER triggers of partitioned tables. Prevent infinite loops in SP-GiST index insertion. Ensure that SP-GiST index insertion can be terminated by a query cancel request. In psql and other client programs, avoid overrunning the ends of strings when dealing with invalidly-encoded data. Fix pg_dump to correctly handle triggers on partitioned tables whose enabled status is different from their parent triggers' status. Avoid "invalid creation date in header" warnings when running pg_restore on a file created in a different time zone. pg_upgrade now carries forward the old installation's oldestXID value and no longer forces an anti-wraparound VACUUM." Extend pg_upgrade to detect and warn about extensions that should be upgraded. Fix contrib/postgres_fdw to better work with generated columns, so long as a generated column in a foreign table represents a generated column in the remote table.
Pullup ticket #6491 - requested by nia databases/postgresql10: build fix databases/postgresql11: build fix databases/postgresql12: build fix databases/postgresql13: build fix Revisions pulled up: - databases/postgresql10/distinfo 1.21 - databases/postgresql10/patches/patch-src_backend_Makefile 1.2 - databases/postgresql11/distinfo 1.16 - databases/postgresql11/patches/patch-src_backend_Makefile 1.2 - databases/postgresql12/distinfo 1.10 - databases/postgresql12/patches/patch-src_backend_Makefile 1.2 - databases/postgresql13/distinfo 1.6 - databases/postgresql13/patches/patch-src_backend_Makefile 1.2 --- Module Name: pkgsrc Committed By: mlelstv Date: Mon Jul 12 09:06:22 UTC 2021 Modified Files: pkgsrc/databases/postgresql10: distinfo pkgsrc/databases/postgresql10/patches: patch-src_backend_Makefile pkgsrc/databases/postgresql11: distinfo pkgsrc/databases/postgresql11/patches: patch-src_backend_Makefile pkgsrc/databases/postgresql12: distinfo pkgsrc/databases/postgresql12/patches: patch-src_backend_Makefile pkgsrc/databases/postgresql13: distinfo pkgsrc/databases/postgresql13/patches: patch-src_backend_Makefile Log Message: Add backends order dependency for catalog -> utils
Add backends order dependency for catalog -> utils
postgresql: updated to 13.3, 12.7, 11.12, 10.17, 9.6.22
PostgreSQL 13.3, 12.7, 11.12, 10.17, and 9.6.22 Released!
Posted on 2021-05-13 by PostgreSQL Global Development Group
PostgreSQL Project Security
The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 13.3, 12.7, 11.12, 10.17, and 9.6.22. This release closes three security vulnerabilities and fixes over 45 bugs reported over the last three months.
For the full list of changes, please review the release notes.
Security Issues
CVE-2021-32027: Buffer overrun from integer overflow in array subscripting calculations
Versions Affected: 9.6 - 13. The security team typically does not test unsupported versions, but this problem is quite old.
While modifying certain SQL array values, missing bounds checks let authenticated database users write arbitrary bytes to a wide area of server memory.
The PostgreSQL project thanks Tom Lane for reporting this problem.
CVE-2021-32028: Memory disclosure in INSERT ... ON CONFLICT ... DO UPDATE
Versions Affected: 9.6 - 13. The security team typically does not test unsupported versions. The feature first appeared in 9.5.
Using an INSERT ... ON CONFLICT ... DO UPDATE command on a purpose-crafted table, an attacker can read arbitrary bytes of server memory. In the default configuration, any authenticated database user can create prerequisite objects and complete this attack at will. A user lacking the CREATE and TEMPORARY privileges on all databases and the CREATE privilege on all schemas cannot use this attack at will.
The PostgreSQL project thanks Andres Freund for reporting this problem.
CVE-2021-32029: Memory disclosure in partitioned-table UPDATE ... RETURNING
Versions Affected: 11 - 13
Using an UPDATE ... RETURNING on a purpose-crafted partitioned table, an attacker can read arbitrary bytes of server memory. In the default configuration, any authenticated database user can create prerequisite objects and complete this attack at will. A user lacking the CREATE and TEMPORARY privileges on all databases and the CREATE privilege on all schemas typically cannot use this attack at will.
The PostgreSQL project thanks Tom Lane for reporting this problem.
Bug Fixes and Improvements
This update fixes over 45 bugs that were reported in the last several months. Some of these issues only affect version 13, but could also apply to other supported versions.
Some of these fixes include:
Fix potential incorrect computation of UPDATE ... RETURNING outputs for joined, cross-partition updates.
Fix ALTER TABLE ... ALTER CONSTRAINT when used on foreign-key constraints on partitioned tables. The command would fail to adjust the DEFERRABLE and/or INITIALLY DEFERRED properties of the constraints and triggers of leaf partitions, leading to unexpected behavior. After updating to this version, you can execute the ALTER TABLE ... ALTER CONSTRAINT command to fix any misbehaving partitioned tables.
Ensure that when a child table is attached with ALTER TABLE ... INHERIT that generated columns in the parent are generated in the same way in the child.
Forbid marking an identity column as NULL.
Allow ALTER ROLE ... SET/ALTER DATABASE ... SET to set the role, session_authorization, and temp_buffers parameters.
Ensure that REINDEX CONCURRENTLY preserves any statistics target set for the index.
Fix an issue where, in some cases, saving records within AFTER triggers could cause crashes.
Fix how to_char() handles Roman-numeral month format codes with negative intervals.
Fix use of uninitialized value while parsing an \{m,n\} quantifier in a BRE-mode regular expression.
Fix "could not find pathkey item to sort" planner errors that occur in some situations when the sort key involves an aggregate or window function.
Fix issue with BRIN index bitmap scans that could lead to "could not open file" errors.
Fix potentially wrong answers from GIN tsvector index searches when there are many matching records.
Fixes for COMMIT AND CHAIN functionality on both the server and psql.
Avoid incorrect timeline change while recovering uncommitted two-phase transactions from WAL, which could lead to consistency issues and the inability to restart the server.
Ensure thatwal_sync_method is set to fdatasync by default on newer FreeBSD releases.
Disable the vacuum_cleanup_index_scale_factor parameter and storage option.
Fix several memory leaks in the server, including one with SSL/TLS parameter initialization.
Restore the previous behavior of \connect service=XYZ to psql, i.e. disallow environmental variables (e.g. PGPORT) from overriding entries in the service file.
Fix how pg_dump handles generated columns in partitioned tables.
Add additional checks to pg_upgrade for user tables containing non-upgradable data types.
On Windows, initdb now prints instructions about how to start the server with pg_ctl using backslash separators.
Fix pg_waldump to count XACT records correctly when generating per-record statistics.
postgresql: fix buildling contrib/uuid-ossp; fixes for LLVM enabled; should fix #55803
postgresql: updated to 13.2, 12.6, 11.11, 10.16, 9.6.21, and 9.5.25 The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 13.2, 12.6, 11.11, 10.16, 9.6.21, and 9.5.25. This release closes two security vulnerabilities and fixes over 80 bugs reported over the last three months. Additionally, this is the final release of PostgreSQL 9.5. If you are running PostgreSQL 9.5 in a production environment, we suggest that you make plans to upgrade. For the full list of changes, please review the release notes. Security Issues CVE-2021-3393: Partition constraint violation errors leak values of denied columns Versions Affected: 11 - 13. A user having an UPDATE privilege on a partitioned table but lacking the SELECT privilege on some column may be able to acquire denied-column values from an error message. This is similar to CVE-2014-8161, but the conditions to exploit are more rare. The PostgreSQL project thanks Heikki Linnakangas for reporting this problem. CVE-2021-20229: Single-column SELECT privilege enables reading all columns Versions Affected: 13. A user having a SELECT privilege on an individual column can craft a special query that returns all columns of the table. Additionally, a stored view that uses column-level privileges will have incomplete column-usage bitmaps. In installations that depend on column-level permissions for security, it is recommended to execute CREATE OR REPLACE on all user-defined views to force them to be re-parsed. The PostgreSQL project thanks Sven Klemm for reporting this problem. Bug Fixes and Improvements This update fixes over 80 bugs that were reported in the last several months. Some of these issues only affect version 13, but could also apply to other supported versions. Some of these fixes include: Fix an issue with GiST indexes where concurrent insertions could lead to a corrupt index with entries placed in the wrong pages. You should REINDEX any affected GiST indexes. Fix CREATE INDEX CONCURRENTLY to ensure rows from concurrent prepared transactions are included in the index. Installations that have enabled prepared transactions should REINDEX any concurrently-built indexes. Fix for possible incorrect query results when a hash aggregation is spilled to disk. Fix edge case in incremental sort that could lead to sorting results incorrectly or a "retrieved too many tuples in a bounded sort" error. Avoid crash when a CALL or DO statement that performs a transaction rollback is executed via extended query protocol, such as from prepared statements. Fix a failure when a PL/pgSQL procedure used CALL on another procedure that has OUT parameters that executed a COMMIT or ROLLBACK. Remove errors from BEFORE UPDATE triggers on partitioned tables for restrictions that no longer apply. Several fixes for queries with joins that could lead to error messages such as "no relation entry for relid N" or "failed to build any N-way joins". Do not consider parallel-restricted or set-returning functions in an ORDER BY expressions when trying to parallelize sorts. Fix ALTER DEFAULT PRIVILEGES to handle duplicate arguments safely. Several fixes in behavior when wal_level is set to minimal, including when tables are rewritten within a transaction. Several fixes for CREATE TABLE LIKE. Ensure that allocated disk space for a dropped relation (e.g. a table) is released promptly when a transaction is committed. Fix progress reporting for CLUSTER. Fix handling of backslash-escaped multibyte characters in COPY FROM. Fix recently-introduced race conditions in LISTEN/NOTIFY queue handling. Allow the jsonb concatenation operator (||) to handle all combinations of JSON data types. Fix WAL-reading logic so that standbys can handle timeline switches correctly. This issue could have shown itself with errors like "requested WAL segment has already been removed". Several leak fixes for the walsender process around logical decoding and replication. Ensure that a nonempty value of krb_server_keyfile always overrides any setting of KRB5_KTNAME in the server environment Several fixes for GSS encryption support. Ensure the \connect command allows the use of a password in the connection_string argument. Fix assorted bugs with the \help command. Several fixes for pg_dump. Ensure that pg_rewind accounts for all WAL when rewinding a standby server. Fix memory leak in contrib/auto_explain. Ensure all postgres_fdw connections are closed if the a user mapping or foreign server object those connections depend on are dropped. Fix JIT compilation to be compatible with LLVM 11 and LLVM 12. This update also contains tzdata release 2021a for DST law changes in Russia (Volgograd zone) and South Sudan, plus historical corrections for Australia, Bahamas, Belize, Bermuda, Ghana, Israel, Kenya, Nigeria, Palestine, Seychelles, and Vanuatu. Notably, the Australia/Currie zone has been corrected to the point where it is identical to Australia/Hobart. For the full list of changes available, please review the release notes. PostgreSQL 9.5 is EOL This is the final release of PostgreSQL 9.5. If you are running PostgreSQL 9.5 in a production environment, we suggest that you make plans to upgrade to a newer, supported version of PostgreSQL. Please see our versioning policy for more information.
postgresql: updated to 13.1, 12.5, 11.10, 10.15, 9.6.20, and 9.5.24 PostgreSQL 13.1, 12.5, 11.10, 10.15, 9.6.20, and 9.5.24 Security Issues * CVE-2020-25695: Multiple features escape "security restricted operation" sandbox * CVE-2020-25694: Reconnection can downgrade connection security settings * CVE-2020-25696: psql's \gset allows overwriting specially treated variables Bug Fixes and Improvements This update also fixes over 65 bugs that were reported in the last several months. Some of these issues only affect version 13, but may also apply to other supported versions. Some of these fixes include: Fix a breakage in the replication protocol by ensuring that two "command completion" events are expected for START_REPLICATION. Ensure fsync is called on the SLRU caches that PostgreSQL maintains. This prevents potential data loss due to an operating system crash. Fix ALTER ROLE usage for users with the BYPASSRLS permission. ALTER TABLE ONLY ... DROP EXPRESSION is disallowed on partitioned tables when there are child tables. Ensure that ALTER TABLE ONLY ... ENABLE/DISABLE TRIGGER does not apply to child tables. Fix for ALTER TABLE ... SET NOT NULL on partitioned tables to avoid a potential deadlock in parallel pg_restore. Fix handling of expressions in CREATE TABLE LIKE with inheritance. DROP INDEX CONCURRENTLY is disallowed on partitioned tables. Allow LOCK TABLE to succeed on a self-referential view instead of throwing an error. Several fixes around statistics collection and progress reporting for REINDEX CONCURRENTLY. Ensure that GENERATED columns are updated when any columns they depend on are updated via a rule or an updatable view. Support hash partitioning with text array columns as partition keys. Allow the jsonpath .datetime() method to accept ISO 8601-format timestamps. During a "smart" shutdown, ensure background processes are not terminated until all foreground client sessions are completed, fixing an issue that broke the processing of parallel queries. Several fixes for the query planner and optimizer. Ensure that data is de-toasted before being inserted into a BRIN index. This could manifest itself with errors like "missing chunk number 0 for toast value NNN". If you have seen a similar error in an existing BRIN index, you should be able to correct it by using REINDEX on the index. Fix the output of EXPLAIN to have the correct XML tag nesting for incremental sort plans. Several fixes for memory leaks, including ones involving RLS policies, using CALL with PL/pgSQL, SIGHUP processing a configuration parameter that cannot be applied without a restart, and an edge-case for index lookup for a partition. libpq can now support arbitrary-length lines in the .pgpass file. On Windows, psql now reads the output of a backtick command in text mode, not binary mode, so it can now properly handle newlines. Fix how pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb use complex connection-string parameters. When the \connect command of psql reuses connection parameters, ensure that all non-overridden parameters from a previous connection string are also re-used. Ensure that pg_dump collects per-column information about extension configuration tables, avoiding crashes when specifying --inserts. Ensure that parallel pg_restore processes foreign keys referencing partitioned tables in the correct order. Several fixes for contrib/pgcrypto, including a memory leak fix.
postgresql: updated to 12.4, 11.9, 10.14, 9.6.19, 9.5.23 PostgreSQL 12.4, 11.9, 10.14, 9.6.19, 9.5.23 Security Issues CVE-2020-14349: Uncontrolled search path element in logical replication. Versions Affected: 10 - 12. The PostgreSQL search_path setting determines schemas searched for tables, functions, operators, etc. The CVE-2018-1058 fix caused most PostgreSQL-provided client applications to sanitize search_path, but logical replication continued to leave search_path unchanged. Users of a replication publisher or subscriber database can create objects in the public schema and harness them to execute arbitrary SQL functions under the identity running replication, often a superuser. Installations having adopted a documented secure schema usage pattern are not vulnerable. The PostgreSQL project thanks Noah Misch for reporting this problem. CVE-2020-14350: Uncontrolled search path element in CREATE EXTENSION. Versions Affected: 9.5 - 12. The security team typically does not test unsupported versions, but this problem is quite old. When a superuser runs certain CREATE EXTENSION statements, users may be able to execute arbitrary SQL functions under the identity of that superuser. The attacker must have permission to create objects in the new extension's schema or a schema of a prerequisite extension. Not all extensions are vulnerable. In addition to correcting the extensions provided with PostgreSQL, the PostgreSQL Global Development Group is issuing guidance for third-party extension authors to secure their own work. Bug Fixes and Improvements This update also fixes over 50 bugs that were reported in the last several months. Some of these issues affect only version 12, but many affect all supported versions. Some of these fixes include: Fix edge cases in partition pruning involving multiple partition key columns with multiple or no constraining WHERE clauses. Several fixes for query planning and execution involving partitions. Fix for determining when to execute a column-specific UPDATE trigger on a logical replication subscriber. pg_replication_slot_advance() now updates the oldest xmin and LSN values, as the failure to do this could prevent resources (e.g. WAL files) from being cleaned up. Fix a performance regression in ts_headline(). Ensure that pg_read_file() and related functions read until EOF is reached, which fixes compatibility with pipes and other virtual files. Forbid numeric NaN values in jsonpath computations, which do not exist in SQL nor JSON. Several fixes for NaN inputs with aggregate functions. This fixes a change in PostgreSQL 12 where NaN values caused the following aggregates to emit values of 0 instead of NaN: corr(), covar_pop(), regr_intercept(), regr_r2(), regr_slope(), regr_sxx(), regr_sxy(), regr_syy(), stddev_pop(), and var_pop(). time and timetz values fractionally greater than 24:00:00 are now rejected. Several fixes for EXPLAIN, including a fix for reporting resource usage when a plan uses parallel workers with "Gather Merge" nodes. Fix timing of constraint revalidation in ALTER TABLE that could lead to odd errors. Fix for REINDEX CONCURRENTLY that could prevent old values from being included in future logical decoding output. Fix for LATERAL references that could potentially cause crashes during query execution. Use the collation specified for a query when estimating operator costs Fix conflict-checking anomalies in SERIALIZABLE transaction isolation mode. Ensure checkpointer process discards file sync requests when fsync is off Fix issue where pg_control could be written out with an inconsistent checksum, which could lead to the inability to restart the database if it crashed before the next pg_control update. Ensure that libpq continues to try to read from the database connection socket after a write failure, as this allows the connection to collect any final error messages from the server. Report out-of-disk-space errors properly in pg_dump and pg_basebackup Several fixes for pg_restore, including a fix for parallel restore on tables that have both table-level and column-level privileges. Fix for pg_upgrade to ensure it runs with vacuum_defer_cleanup_age set to 0. Fix how pg_rewind handles just-deleted files in the source data directory Fix failure to initialize local state correctly in contrib/dblink, which could lead to dblink_close() issuing an unexpected COMMIT on the remote server. Change contrib/amcheck to not report about deleted index pages that are empty, as this is normal during WAL replay.
postgresqlNN: updated to 12.3, 11.8, 10.13, 9.6.18, and 9.5.22 PostgreSQL 12.3, 11.8, 10.13, 9.6.18, and 9.5.22 Released! Posted on 2020-05-14 by PostgreSQL Global Development Group The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 12.3, 11.8, 10.13, 9.6.18, and 9.5.22. This release fixes one security issue found in the PostgreSQL server and over 75 bugs reported over the last three months. Please plan to update at your earliest convenience. Security Issues CVE-2020-10733: Windows installer runs executables from uncontrolled directories. Versions Affected: 9.5 - 12. The security team does not test unsupported versions, but this issue existed before PostgreSQL 9.5. The Windows installer for PostgreSQL invokes system-provided executables that do not have fully-qualified paths. Executables in the directory where the installer loads or the current working directory take precedence over the intended executables. An attacker having permission to add files into one of those directories can use this to execute arbitrary code with the installer's administrative rights. The PostgreSQL project thanks Hou JingYi (@hjy79425575) for reporting this problem. Bug Fixes and Improvements This update also fixes over 75 bugs that were reported in the last several months. Some of these issues affect only version 12, but may also affect all supported versions. Some of these fixes include: Several fixes for GENERATED columns, including an issue where it was possible to crash or corrupt data in a table when the output of the generated column was the exact copy of a physical column on the table, e.g. if the expression called a function which could return its own input. Several fixes for ALTER TABLE, including ensuring the SET STORAGE directive is propagated to a table's indexes. Fix a potential race condition when using DROP OWNED BY while another session is deleting the same objects. Allow for a partition to be detached when it has inherited ROW triggers. Several fixes for REINDEX CONCURRENTLY, particularly with issues when a REINDEX CONCURRENTLY operation fails. Fix crash when COLLATE is applied to an uncollatable type in a partition bound expression. Fix performance regression in floating point overflow/underflow detection. Several fixes for full text search, particularly with phrase searching. Fix query-lifespan memory leak for a set-returning function used in a query's FROM clause. Several reporting fixes for the output of VACUUM VERBOSE. Allow input of type circle to accept the format (x,y),r, which is specified in the documentation. Allow for the get_bit() and set_bit() functions to not fail on bytea strings longer than 256MB. Avoid premature recycling of WAL segments during crash recovery, which could lead to WAL segments being recycled before being archived. Avoid attempting to fetch nonexistent WAL files from archive storage during recovery by skipping irrelevant timelines. Several fixes for logical replication and replication slots. Fix several race conditions in synchronous standby management, including one that occurred when changing the synchronous_standby_names setting. Several fixes for GSSAPI support, include a fix for a memory leak that occurred when using GSSAPI encryption. Ensure that members of the pg_read_all_stats role can read all statistics views. Fix performance regression in information_schema.triggers view. Fix memory leak in libpq when using sslmode=verify-full. Fix crash in psql when attempting to re-establish a failed connection. Allow tab-completion of the filename argument to \gx command in psql. Add pg_dump support for ALTER ... DEPENDS ON EXTENSION. Several other fixes for pg_dump, which include dumping comments on RLS policies and postponing restore of event triggers until the end. Ensure pg_basebackup generates valid tar files. pg_checksums skips tablespace subdirectories that belong to a different PostgreSQL major version Several Windows compatibility fixes This update also contains tzdata release 2020a for DST law changes in Morocco and the Canadian Yukon, plus historical corrections for Shanghai. The America/Godthab zone has been renamed to America/Nuuk to reflect current English usage ; however, the old name remains available as a compatibility link. This also updates initdb's list of known Windows time zone names to include recent additions.
postgresqlNN: updated to 12.2, 11.7, 10.12, 9.6.17, 9.5.21, and 9.4.26 PostgreSQL 12.2, 11.7, 10.12, 9.6.17, 9.5.21, and 9.4.26 PostgreSQL 9.4 Now EOL This is the last release for PostgreSQL 9.4, which will no longer receive security updates and bug fixes. PostgreSQL 9.4 introduced new features such as JSONB support, the ALTER SYSTEM command, the ability to stream logical changes to an output plugin, and more. While we are very proud of this release, these features are also found in newer versions of PostgreSQL. Many of these features have also received improvements, and, per our versioning policy, it is time to retire PostgreSQL 9.4. To receive continued support, we suggest that you make plans to upgrade to a newer, supported version of PostgreSQL. Please see the PostgreSQL versioning policy for more information. Security Issues CVE-2020-1720: ALTER ... DEPENDS ON EXTENSION is missing authorization checks. Versions Affected: 9.6 - 12 The ALTER ... DEPENDS ON EXTENSION sub-commands do not perform authorization checks, which can allow an unprivileged user to drop any function, procedure, materialized view, index, or trigger under certain conditions. This attack is possible if an administrator has installed an extension and an unprivileged user can CREATE, or an extension owner either executes DROP EXTENSION predictably or can be convinced to execute DROP EXTENSION. Bug Fixes and Improvements This update also fixes over 75 bugs that were reported in the last several months. Some of these issues affect only version 12, but may also affect all supported versions. Some of these fixes include: Fix for partitioned tables with foreign-key references where TRUNCATE ... CASCADE would not remove all data. If you have previously used TRUNCATE ... CASCADE on a partitioned table with foreign-key references please see the "Updating" section for verification and cleanup steps. Fix failure to add foreign key constraints to table with sub-partitions (aka a multi-level partitioned table). If you have previously used this functionality, you can fix it by either detaching and re-attaching the affected partition, or by dropping and re-adding the foreign key constraint to the parent table. You can find more information on how to perform these steps in the ALTER TABLE documentation. Fix performance issue for partitioned tables introduced by the fix for CVE-2017-7484 that now allows the planner to use statistics on a child table for a column that the user is granted access to on the parent table when the query contains a leaky operator. Several other fixes and changes for partitioned tables, including disallowing partition key expressions that return pseudo-types, such as RECORD. Fix for logical replication subscribers for executing per-column UPDATE triggers. Fix for several crashes and failures for logical replication subscribers and publishers. Improve efficiency of logical replication with REPLICA IDENTITY FULL. Ensure that calling pg_replication_slot_advance() on a physical replication slot will persist changes across restarts. Several fixes for the walsender processes. Improve performance of hash joins with very large inner relations. Fix placement of "Subplans Removed" field in EXPLAIN output by placing it with its parent Append or MergeAppend plan. Several fixes for parallel query plans. Several fixes for query planner errors, including one that affected joins to single-row subqueries. Several fixes for MCV extend statistics, including one for incorrect estimation for OR clauses. Improve efficiency of parallel hash join on CPUs with many cores. Ignore the CONCURRENTLY option when performing an index creation, drop, or reindex on a temporary table. Fall back to non-parallel index builds when a parallelized CREATE INDEX has no free dynamic shared memory slots. Several fixes for GiST & GIN indexes. Fix possible crash in BRIN index operations with box, range and inet data types. Fix support for BRIN hypothetical indexes. Fix failure in ALTER TABLE when a column referenced in a GENERATED expression is added or changed in type earlier in the same ALTER TABLE statement. Fix handling of multiple AFTER ROW triggers on a foreign table. Fix off-by-one result for EXTRACT(ISOYEAR FROM timestamp) for BC dates. Prevent unwanted lowercasing and truncation of RADIUS authentication parameters in the pg_hba.conf file. Several fixes for GSSAPI support, including having libpq accept all GSS-related connection parameters even if the GSSAPI code is not compiled in. Several fixes for pg_dump and pg_restore when run in parallel mode. Fix crash with postgres_fdw when trying to execute a remote query on the remote server such as UPDATE remote_tab SET (x,y) = (SELECT ...). Disallow NULL category values in the crosstab() function of contrib/tablefunc to prevent crashes. Several fixes for Windows, including a race condition that could cause timing oddities with NOTIFY. Several ecpg fixes.
postgresqlNN: updated to 12.1, 11.6, 10.11, 9.6.16, 9.5.20, and 9.4.25 PostgreSQL 12.1, 11.6, 10.11, 9.6.16, 9.5.20, and 9.4.25 Released! PostgreSQL 9.4 EOL Approaching PostgreSQL 9.4 will stop receiving fixes on February 13, 2020, which is the next planned cumulative update release. Please see our versioning policy for more information. Bug Fixes and Improvements This update also fixes over 50 bugs that were reported in the last several months. Some of these issues affect only version 12, but may also affect all supported versions. Some of these fixes include: Fix crash that occurs when ALTER TABLE adds a column without a default value along with other changes that require a table rewrite Several fixes for REINDEX CONCURRENTLY. Fix for VACUUM that would cause it to fail under a specific case involving a still-running transaction. Fix for a memory leak that could occur when VACUUM runs on a GiST index. Fix for an error that occurred when running CLUSTER on an expression index. Fix failure for SET CONSTRAINTS ... DEFERRED on partitioned tables. Several fixes for the creation and dropping of indexes on partitioned tables. Fix for partition-wise joins that could lead to planner failures. Ensure that offset expressions in WINDOW clauses are processed when a query's expressions are manipulated. Fix misbehavior of bitshiftright() where it failed to zero out padding space in the last byte if the bit string length is not a multiple of 8. For how to correct your data, please see the "Updating" section. Ensure an empty string that is evaluated by the position() functions returns 1, as per the SQL standard. Fix for a parallel query failure when it is unable to request a background worker. Fix crash triggered by a case involving a BEFORE UPDATE trigger. Display the correct error when a query tries to access a TOAST table. Allow encoding conversion to succeed on strings with output up to 1GB. Previously there was hard limit of 0.25GB on the input string. Ensure that temporary WAL and history files are removed at the end of archive recovery. Avoid failure in archive recovery if recovery_min_apply_delay is enabled. Ignore restore_command, recovery_end_command, and recovery_min_apply_delay settings during crash recovery. Several fixes for logical replication, including a failure when the publisher and subscriber had different REPLICA IDENTITY columns set. Correctly timestamp replication messages for logical decoding, which in the broken case would lead to pg_stat_subscription.last_msg_send_time set to NULL. Several fixes for libpq, including one that improves PostgreSQL 12 compatibility. Several pg_upgrade fixes. Fix how a parallel restore handles foreign key constraints on partitioned tables to ensure they are not created too soon. pg_dump now outputs similarly named triggers and RLS policies in order based on table name, instead of OID. Fix pg_rewind to not update the contents of pg_control when using the --dry-run option. This update also contains tzdata release 2019c for DST law changes in Fiji and Norfolk Island. Historical corrections for Alberta, Austria, Belgium, British Columbia, Cambodia, Hong Kong, Indiana (Perry County), Kaliningrad, Kentucky, Michigan, Norfolk Island, South Korea, and Turkey.
postgresql12: added version 12.0 Release 12: General performance improvements, including: * Optimizations to space utilization and read/write performance for B-tree indexes * Partitioning performance enhancements, including improved query performance on tables with thousands of partitions, improved insertion performance with INSERT and COPY, and the ability to execute ALTER TABLE ATTACH PARTITION without blocking queries * Automatic (but overridable) inlining of common table expressions (CTEs) * Reduction of WAL overhead for creation of GiST, GIN, and SP-GiST indexes * Support for covering GiST indexes, via the INCLUDE clause * Multi-column most-common-value (MCV) statistics can be defined via CREATE STATISTICS, to support better plans for queries that test several non-uniformly-distributed columns Enhancements to administrative functionality, including: * REINDEX CONCURRENTLY can rebuild an index without blocking writes to its table * pg_checksums can enable/disable page checksums (used for detecting data corruption) in an offline cluster * Progress reporting statistics for CREATE INDEX, REINDEX, CLUSTER, VACUUM FULL, and pg_checksums Support for the SQL/JSON path language Stored generated columns Nondeterministic ICU collations, enabling case-insensitive and accent-insensitive grouping and ordering New authentication features, including: * Encryption of TCP/IP connections when using GSSAPI authentication * Discovery of LDAP servers using DNS SRV records * Multi-factor authentication, using the clientcert=verify-full option combined with an additional authentication method in pg_hba.conf