+
+
Release 14.14
+
+
+
Release date:
+
+
+ This release contains a variety of fixes from 14.13.
+ For information about new features in major release 14, see
+ .
+
+
+
+
Migration to Version 14.14
+
+ A dump/restore is not required for those running 14.X.
+
+
+ However, if you have ever detached a partition from a partitioned
+ table that has a foreign-key reference to another partitioned table,
+ and not dropped the former partition, then you may have catalog and/or
+ data corruption to repair, as detailed in the first changelog entry
+ below.
+
+
+ Also, if you are upgrading from a version earlier than 14.12,
+ see .
+
+
+
+
+
Changes
+
+
+
+
+
+ Fix updates of catalog state for foreign-key constraints when
+ attaching or detaching table partitions (Jehan-Guillaume de
+ Rorthais, Tender Wang, Álvaro Herrera)
+
+
+ If the referenced table is partitioned, then different catalog
+ entries are needed for a referencing table that is stand-alone
+ versus one that is a partition. ATTACH/DETACH
+ PARTITION commands failed to perform this conversion
+ correctly. In particular, after DETACH the now
+ stand-alone table would be missing foreign-key enforcement triggers,
+ which could result in the table later containing rows that fail the
+ foreign-key constraint. A subsequent re-ATTACH
+ could fail with surprising errors, too.
+
+
+ The way to fix this is to do ALTER TABLE DROP
+ CONSTRAINT on the now stand-alone table for each faulty
+ constraint, and then re-add the constraint. If re-adding the
+ constraint fails, then some erroneous data has crept in. You will
+ need to manually re-establish consistency between the referencing
+ and referenced tables, then re-add the constraint.
+
+
+ This query can be used to identify broken constraints and construct
+ the commands needed to recreate them:
+SELECT conrelid::pg_catalog.regclass AS "constrained table",
+ conname AS constraint,
+ confrelid::pg_catalog.regclass AS "references",
+ pg_catalog.format('ALTER TABLE %s DROP CONSTRAINT %I;',
+ conrelid::pg_catalog.regclass, conname) AS "drop",
+ pg_catalog.format('ALTER TABLE %s ADD CONSTRAINT %I %s;',
+ conrelid::pg_catalog.regclass, conname,
+ pg_catalog.pg_get_constraintdef(oid)) AS "add"
+FROM pg_catalog.pg_constraint c
+WHERE contype = 'f' AND conparentid = 0 AND
+ (SELECT count(*) FROM pg_catalog.pg_constraint c2
+ WHERE c2.conparentid = c.oid) <>
+ (SELECT count(*) FROM pg_catalog.pg_inherits i
+ WHERE (i.inhparent = c.conrelid OR i.inhparent = c.confrelid) AND
+ EXISTS (SELECT 1 FROM pg_catalog.pg_partitioned_table
+ WHERE partrelid = i.inhparent));
+
+ Since it is possible that one or more of the ADD
+ CONSTRAINT steps will fail, you should save the query's
+ output in a file and then attempt to perform each step.
+
+
+
+
+
+ Avoid possible crashes and could not open relation
+ errors in queries on a partitioned table occurring concurrently with
+ a DETACH CONCURRENTLY and immediate drop of a
+ partition (Álvaro Herrera, Kuntal Gosh)
+
+
+
+
+
+ Disallow ALTER TABLE ATTACH PARTITION if the
+ table to be attached has a foreign key referencing the partitioned
+ table (Álvaro Herrera)
+
+
+ This arrangement is not supported, and other ways of creating it
+ already fail.
+
+
+
+
+
+ Don't use partitionwise joins or grouping if the query's collation
+ for the key column doesn't match the partition key's collation (Jian
+ He, Webbo Han)
+
+
+ Such plans could produce incorrect results.
+
+
+
+
+
+ Fix possible could not find pathkey item to sort
+ error when the output of a UNION ALL member query
+ needs to be sorted, and the sort column is an expression (Andrei
+ Lepikhov, Tom Lane)
+
+
+
+
+
+ Allow cancellation of the second stage of index build for large hash
+ indexes (Pavel Borisov)
+
+
+
+
+
+ Fix assertion failure or confusing error message for COPY
+ (query) TO ..., when
+ the query is rewritten by a DO
+ INSTEAD NOTIFY rule (Tender Wang, Tom Lane)
+
+
+
+
+
+ Fix detection of skewed data during parallel hash join (Thomas
+ Munro)
+
+
+ After repartitioning the inner side of a hash join because one
+ partition has accumulated too many tuples, we check to see if all
+ the partition's tuples went into the same child partition, which
+ suggests that they all have the same hash value and further
+ repartitioning cannot improve matters. This check malfunctioned in
+ some cases, allowing repeated futile repartitioning which would
+ eventually end in a resource-exhaustion error.
+
+
+
+
+
+ Fix race condition in committing a serializable transaction (Heikki
+ Linnakangas)
+
+
+ Mis-processing of a recently committed transaction could lead to an
+ assertion failure or a could not access status of
+ transaction error.
+
+
+
+
+
+ Fix race condition in COMMIT PREPARED
+ that resulted in orphaned 2PC files (wuchengwen)
+
+
+ A concurrent PREPARE TRANSACTION could
+ cause COMMIT PREPARED to not remove the on-disk
+ two-phase state file for the completed transaction. There was no
+ immediate ill effect, but a subsequent crash-and-recovery could fail
+ with could not access status of transaction
,
+ requiring manual removal of the orphaned file to restore service.
+
+
+
+
+
+ Avoid invalid memory accesses after skipping an invalid toast index
+ during VACUUM FULL (Tender Wang)
+
+
+ A list tracking yet-to-be-rebuilt indexes was not properly updated
+ in this code path, risking assertion failures or crashes later on.
+
+
+
+
+
+ Fix ways in which an in place
catalog update could be
+ lost (Noah Misch)
+
+
+ Normal row updates write a new version of the row to preserve
+ rollback-ability of the transaction. However, certain system
+ catalog updates are intentionally non-transactional and are done
+ with an in-place update of the row. These patches fix race
+ conditions that could cause the effects of an in-place update to be
+ lost. As an example, it was possible to forget having set
+ pg_class.relhasindex
+ to true, preventing updates of the new index and thus causing index
+ corruption.
+
+
+
+
+
+ Reset catalog caches at end of recovery (Noah Misch)
+
+
+ This prevents scenarios wherein an in-place catalog update could be
+ lost due to using stale data from a catalog cache.
+
+
+
+
+
+ Avoid using parallel query while holding off interrupts
+ (Francesco Degrassi, Noah Misch, Tom Lane)
+
+
+ This situation cannot arise normally, but it can be reached with
+ test scenarios such as using a SQL-language function as B-tree
+ support (which would be far too slow for production usage). If it
+ did occur it would result in an indefinite wait.
+
+
+
+
+
+ Report the active query ID for statistics purposes at the start of
+ processing of Bind and Execute protocol messages (Sami Imseih)
+
+
+ This allows more of the work done in extended query protocol to be
+ attributed to the correct query.
+
+
+
+
+
+ Guard against stack overflow in
libxml2+ with too-deeply-nested XML input (Tom Lane, with hat tip to Nick
+ Wellnhofer)
+
+
+ Use xmlXPathCtxtCompile() rather
+ than xmlXPathCompile(), because the latter
+ fails to protect itself against recursion-to-stack-overflow
+ in
libxml2 releases before 2.13.4.
+
+
+
+
+
+ Do not ignore a concurrent REINDEX CONCURRENTLY
+ that is working on an index with predicates or expressions (Michail
+ Nikolaev)
+
+
+ Normally, REINDEX CONCURRENTLY does not need to
+ wait for other REINDEX CONCURRENTLY operations on
+ other tables. However, this optimization is not applied if the
+ other REINDEX CONCURRENTLY is processing an index
+ with predicates or expressions, on the chance that such expressions
+ contain user-defined code that accesses other tables. Careless
+ coding created a race condition such that that rule was not applied
+ uniformly, possibly allowing inconsistent behavior.
+
+
+
+
+
+ Fix failed to find plan for subquery/CTE
errors
+ in EXPLAIN (Richard Guo, Tom Lane)
+
+
+ This case arose while trying to print references to fields of a
+ RECORD-type output of a subquery when the subquery has been
+ optimized out of the plan altogether (which is possible at least in
+ the case that it has a constant-false WHERE
+ condition). Nothing remains in the plan to identify the original
+ field names, so fall back to
+ printing fN for
+ the N'th record column. (That's actually
+ the right thing anyway, if the record output arose from
+ a ROW() constructor.)
+
+
+
+
+
+ Disallow a USING clause when altering the type of
+ a generated column (Peter Eisentraut)
+
+
+ A generated column already has an expression specifying the column
+ contents, so including USING doesn't make sense.
+
+
+
+
+
+ Ignore not-yet-defined Portals in
+ the pg_cursors view (Tom Lane)
+
+
+ It is possible for user-defined code that inspects this view to be
+ called while a new cursor is being set up, and if that happens a
+ null pointer dereference would ensue. Avoid the problem by defining
+ the view to exclude incompletely-set-up cursors.
+
+
+
+
+
+ Avoid unexpected table_index_fetch_tuple call during logical
+ decoding error while decoding a transaction involving
+ insertion of a column default value (Takeshi Ideriha, Hou Zhijie)
+
+
+
+
+
+ Reduce memory consumption of logical decoding (Masahiko Sawada)
+
+
+ Use a smaller default block size to store tuple data received during
+ logical replication. This reduces memory wastage, which has been
+ reported to be severe while processing long-running transactions,
+ even leading to out-of-memory failures.
+
+
+
+
+
+ Re-disable sending of stateless (TLSv1.2) session tickets
+ (Daniel Gustafsson)
+
+
+ A previous change to prevent sending of stateful (TLSv1.3) session
+ tickets accidentally re-enabled sending of stateless ones. Thus,
+ while we intended to prevent clients from thinking that TLS session
+ resumption is supported, some still did.
+
+
+
+
+
+ Avoid wrong tuple length
failure when dropping a
+ database with many ACL (permission) entries (Ayush Tiwari)
+
+
+
+
+
+ Allow adjusting the session_authorization
+ and role settings in parallel workers (Tom Lane)
+
+
+ Our code intends to allow modifiable server settings to be set by
+ function SET clauses, but not otherwise within a
+ parallel worker. SET clauses failed for these
+ two settings, though.
+
+
+
+
+
+ Fix behavior of stable functions called from
+ a CALL statement's argument list, when
+ the CALL is within a
+ PL/pgSQL EXCEPTION block (Tom Lane)
+
+
+ As with a similar fix in our previous quarterly releases, this case
+ allowed such functions to be passed the wrong snapshot, causing them
+ to see stale values of rows modified since the start of the outer
+ transaction.
+
+
+
+
+
+ Fix cache lookup failed for function
errors in edge
+ cases in PL/pgSQL's CALL (Tom Lane)
+
+
+
+
+
+ Fix thread safety of our fallback (non-OpenSSL) MD5 implementation
+ on big-endian hardware (Heikki Linnakangas)
+
+
+ Thread safety is not currently a concern in the server, but it is
+ for libpq.
+
+
+
+
+
+ Parse
libpq's
keepalives+ connection option in the same way as other integer-valued options
+ (Yuto Sasaki)
+
+
+ The coding used here rejected trailing whitespace in the option
+ value, unlike other cases. This turns out to be problematic
+ in
ecpg's usage, for example.
+
+
+
+
+
+ Avoid use of pnstrdup()
+ in
ecpglib (Jacob Champion)
+
+
+ That function will call exit() on
+ out-of-memory, which is undesirable in a library. The calling code
+ already handles allocation failures properly.
+
+
+
+
+
+ In
ecpglib, fix out-of-bounds read when
+ parsing incorrect datetime input (Bruce Momjian, Pavel Nekrasov)
+
+
+ It was possible to try to read the location just before the start of
+ a constant array. Real-world consequences seem minimal, though.
+
+
+
+
+
+ Include the source timeline history
+ in
pg_rewind's debug output
+ (Heikki Linnakangas)
+
+
+ This was the intention to begin with, but a coding error caused the
+ source history to always print as empty.
+
+
+
+
+
+ Fix misbehavior with junction points on Windows, particularly
+ in
pg_rewind (Alexandra Wang)
+
+
+ This entailed back-patching previous fixes by Thomas Munro, Peter
+ Eisentraut, Alexander Lakhin, and Juan José Santamaría Flecha.
+ Those changes were originally not back-patched out of caution, but
+ they have been in use in later branches for long enough to deem
+ them safe.
+
+
+
+
+
+ Avoid trying to reindex temporary tables and indexes
+ parallel
reindexdb (VaibhaveS, Michael
+ Paquier, Fujii Masao, Nathan Bossart)
+
+
+ Reindexing other sessions' temporary tables cannot work, but the
+ check to skip them was missing in some code paths, leading to
+ unwanted failures.
+
+
+
+
+
+ Allow inspection of sequence relations in relevant functions
+ of contrib/pageinspect
+ and contrib/pgstattuple (Nathan Bossart, Ayush
+ Vatsa)
+
+
+ This had been allowed in the past, but it got broken during the
+ introduction of non-default access methods for tables.
+
+
+
+
+
+ Fix incorrect LLVM-generated code on ARM64 platforms (Thomas
+ Munro, Anthonin Bonnefoy)
+
+
+ When using JIT compilation on ARM platforms, the generated code
+ could not support relocation distances exceeding 32 bits, allowing
+ unlucky placement of generated code to cause server crashes on
+ large-memory systems.
+
+
+
+
+
+ Fix a few places that assumed that process start time (represented
+ as a time_t) will fit into a long value
+ (Max Johnson, Nathan Bossart)
+
+
+ On platforms where long is 32 bits (notably Windows),
+ this coding would fail after Y2038. Most of the failures appear
+ only cosmetic, but notably pg_ctl start would
+ hang.
+
+
+
+
+
+ Prevent nothing provides
+ perl(PostgreSQL::Test::Utils) failures while building RPM
+ packages of
PostgreSQL (Noah Misch)
+
+
+
+
+
+ Fix building with Strawberry Perl on Windows (Andrew Dunstan)
+
+
+
+
+
+ Update time zone data files to
tzdata+ release 2024b (Tom Lane)
+
+
+ This
tzdata release changes the old
+ System-V-compatibility zone names to duplicate the corresponding
+ geographic zones; for example PST8PDT is now an
+ alias for America/Los_Angeles. The main visible
+ consequence is that for timestamps before the introduction of
+ standardized time zones, the zone is considered to represent local
+ mean solar time for the named location. For example,
+ in PST8PDT, timestamptz input such
+ as 1801-01-01 00:00 would previously have been
+ rendered as 1801-01-01 00:00:00-08, but now it is
+ rendered as 1801-01-01 00:00:00-07:52:58.
+
+
+ Also, historical corrections for Mexico, Mongolia, and Portugal.
+ Notably, Asia/Choibalsan is now an alias
+ for Asia/Ulaanbaatar rather than being a separate
+ zone, mainly because the differences between those zones were found to
+ be based on untrustworthy data.
+
+
+
+
+
+
+
+
Release 14.13
projects / postgresql.git / commitdiff