+
+
Release 14.9
+
+
+
Release date:
+
+
+ This release contains a variety of fixes from 14.8.
+ For information about new features in major release 14, see
+ .
+
+
+
+
Migration to Version 14.9
+
+ A dump/restore is not required for those running 14.X.
+
+
+ However, if you use BRIN indexes, it may be advisable to reindex them;
+ see the first changelog entry below.
+
+
+ Also, if you are upgrading from a version earlier than 14.4,
+ see .
+
+
+
+
+
Changes
+
+
+
+
+
+ Fix confusion between empty (no rows) ranges and all-NULL ranges in
+ BRIN indexes, as well as incorrect merging of all-NULL summaries
+ (Tomas Vondra)
+
+
+ Each of these oversights could result in forgetting that a BRIN
+ index range contains any NULL values, potentially allowing
+ subsequent queries that should return NULL values to miss doing so.
+
+
+ This fix will not in itself correct faulty BRIN entries.
+ It's recommended to REINDEX any BRIN indexes that
+ may be used to search for nulls.
+
+
+
+
+
+ Avoid leaving a corrupted database behind when DROP
+ DATABASE is interrupted (Andres Freund)
+
+
+ If DROP DATABASE was interrupted after it had
+ already begun taking irreversible steps, the target database
+ remained accessible (because the removal of
+ its pg_database row would roll back),
+ but it would have corrupt contents. Fix by marking the database
+ as inaccessible before we begin to perform irreversible operations.
+ A failure after that will leave the database still partially
+ present, but nothing can be done with it except to issue
+ another DROP DATABASE.
+
+
+
+
+
+ Ensure that partitioned indexes are correctly marked as valid or not
+ at creation (Michael Paquier)
+
+
+ If a new partitioned index matches an existing but invalid index on
+ one of the partitions, the partitioned index could end up being
+ marked valid prematurely. This could lead to misbehavior or
+ assertion failures in subsequent queries on the partitioned table.
+
+
+
+
+
+ Ignore invalid child indexes when matching partitioned indexes to
+ child indexes during ALTER TABLE ATTACH PARTITION
+ (Michael Paquier)
+
+
+ Such an index will now be ignored, and a new child index created
+ instead.
+
+
+
+
+
+ Fix possible failure when marking a partitioned index valid after
+ all of its partitions have been attached (Michael Paquier)
+
+
+ The update of the index's pg_index entry
+ could use stale data for other columns. One reported symptom is
+ an attempted to update invisible tuple
error.
+
+
+
+
+
+ Fix ALTER EXTENSION SET SCHEMA to complain if the
+ extension contains any objects outside the extension's schema
+ (Michael Paquier, Heikki Linnakangas)
+
+
+ Erroring out if the extension contains objects in multiple schemas
+ was always intended; but the check was mis-coded so that it would
+ fail to detect some cases, leading to surprising behavior.
+
+
+
+
+
+ Don't use partial unique indexes for uniqueness proofs in the
+ planner (David Rowley)
+
+
+ This could give rise to incorrect plans, since the presumed
+ uniqueness of rows read from a table might not hold if the index in
+ question isn't used to scan the table.
+
+
+
+
+
+ Avoid producing incorrect plans for foreign joins with
+ pseudoconstant join clauses (Etsuro Fujita)
+
+
+ The planner currently lacks support for attaching pseudoconstant
+ join clauses to a pushed-down remote join, so disable generation
+ of remote joins in such cases. (A better solution will require
+ ABI-breaking changes of planner data structures, so it will have to
+ wait for a future major release.)
+
+
+
+
+
+ Correctly handle sub-SELECTs in RLS policy expressions and
+ security-barrier views when expanding rule actions (Tom Lane)
+
+
+
+
+
+ Fix race conditions in conflict detection
+ for SERIALIZABLE isolation mode
+ (Thomas Munro)
+
+
+ Conflicts could be missed when using bitmap heap scans, when using
+ GIN indexes, and when examining an initially-empty btree index.
+ All these cases could lead to serializability failures due to
+ improperly allowing conflicting transactions to commit.
+
+
+
+
+
+ Fix misbehavior of EvalPlanQual checks with inherited or partitioned
+ target tables (Tom Lane)
+
+
+ This oversight could lead to update or delete actions
+ in READ COMMITTED isolation mode getting
+ performed when they should have been skipped because of a
+ conflicting concurrent update.
+
+
+
+
+
+ Fix hash join with an inner-side hash key that contains Params
+ coming from an outer nested loop (Tom Lane)
+
+
+ When rescanning the join after the values of such Params have
+ changed, we must rebuild the hash table, but neglected to do so.
+ This could result in missing join output rows.
+
+
+
+
+
+ Fix intermittent failures when trying to update a field of a
+ composite column (Tom Lane)
+
+
+ If the overall value of the composite column is wide enough to
+ require out-of-line toasting, then an unluckily-timed cache flush
+ could cause errors or server crashes.
+
+
+
+
+
+ Prevent query-lifespan memory leaks in some UPDATE
+ queries with triggers (Tomas Vondra)
+
+
+
+
+
+ Prevent query-lifespan memory leaks when an Incremental Sort plan
+ node is rescanned (James Coleman, Laurenz Albe, Tom Lane)
+
+
+
+
+
+ Accept fractional seconds in the input to jsonpath's
+ datetime() method (Tom Lane)
+
+
+
+
+
+ Prevent stack-overflow crashes with very complex text search
+ patterns (Tom Lane)
+
+
+
+
+
+ Allow tokens up to 10240 bytes long
+ in pg_hba.conf
+ and pg_ident.conf (Tom Lane)
+
+
+ The previous limit of 256 bytes has been found insufficient for some
+ use-cases.
+
+
+
+
+
+ Fix mishandling of C++ out-of-memory conditions (Heikki Linnakangas)
+
+
+ If JIT is in use, running out of memory in a
+ C++ new call would lead to
+ a
PostgreSQL FATAL error, instead of the
+ expected C++ exception.
+
+
+
+
+
+ Fix rare null-pointer crash in plancache.c
+ (Tom Lane)
+
+
+
+
+
+ Avoid losing track of possibly-useful shared memory segments when a
+ page free results in coalescing ranges of free space (Dongming Liu)
+
+
+ Ensure that the segment is moved into the
+ appropriate bin
for its new amount of free space, so
+ that it will be found by subsequent searches.
+
+
+
+
+
+ Allow VACUUM to continue after detecting certain
+ types of b-tree index corruption (Peter Geoghegan)
+
+
+ If an invalid sibling-page link is detected, log the issue and press
+ on, rather than throwing an error as before. Nothing short
+ of REINDEX will fix the broken index, but
+ preventing VACUUM from completing until that is
+ done risks making matters far worse.
+
+
+
+
+
+ Ensure that WrapLimitsVacuumLock is released
+ after VACUUM detects invalid data
+ in pg_database.datfrozenxid
+ or pg_database.datminmxid
+ (Andres Freund)
+
+
+ Failure to release this lock could lead to a deadlock later,
+ although the lock would be cleaned up if the session exits or
+ encounters some other error.
+
+
+
+
+
+ Avoid double replay of prepared transactions during crash
+ recovery (suyu.cmj, Michael Paquier)
+
+
+ After a crash partway through a checkpoint with some two-phase
+ transaction state data already flushed to disk by this checkpoint,
+ crash recovery could attempt to replay the prepared transaction(s)
+ twice, leading to a fatal error such as lock is already
+ held in the startup process.
+
+
+
+
+
+ Fix possible failure while promoting a standby server, if archiving
+ is enabled and two-phase transactions need to be recovered (Julian
+ Markwort)
+
+
+ If any required two-phase transactions were logged in the most
+ recent (partial) log segment, promotion would fail with an incorrect
+ complaint about requested WAL segment has already been
+ removed.
+
+
+
+
+
+ Ensure that a newly created, but still empty table
+ is fsync'ed at the next checkpoint (Heikki
+ Linnakangas)
+
+
+ Without this, if there is an operating system crash causing the
+ empty file to disappear, subsequent operations on the table might
+ fail with could not open file
errors.
+
+
+
+
+
+ Ensure that creation of the init fork of an unlogged index is
+ WAL-logged (Heikki Linnakangas)
+
+
+ While an unlogged index's main data fork is not WAL-logged, its init
+ fork should be, to ensure that we have a consistent state to restore
+ the index to after a crash. This step was missed if the init fork
+ contains no data, which is a case not used by any standard index AM;
+ but perhaps some extension behaves that way.
+
+
+
+
+
+ Fix missing reinitializations of delay-checkpoint-end flags
+ (suyu.cmj)
+
+
+ This could result in unnecessary delays of checkpoints, or in
+ assertion failures in assert-enabled builds.
+
+
+
+
+
+ Fix overly strict assertion in jsonpath code
+ (David Rowley)
+
+
+ This assertion failed if a query applied
+ the .type() operator to
+ a like_regex result.
+ There was no bug in non-assert builds.
+
+
+
+
+
+ Avoid assertion failure when processing an empty statement via the
+ extended query protocol in an already-aborted transaction (Tom Lane)
+
+
+
+
+
+ Fix contrib/fuzzystrmatch's
+ Soundex difference() function to handle empty
+ input sanely (Alexander Lakhin, Tom Lane)
+
+
+ An input string containing no alphabetic characters resulted in
+ unpredictable output.
+
+
+
+
+
+ Tighten whitespace checks in contrib/hstore
+ input (Evan Jones)
+
+
+ In some cases, characters would be falsely recognized as whitespace
+ and hence discarded.
+
+
+
+
+
+ Disallow oversize input arrays
+ with contrib/intarray's
+ gist__int_ops index opclass (Ankit Kumar Pandey,
+ Alexander Lakhin)
+
+
+ Previously this code would report a NOTICE but
+ press on anyway, creating an invalid index entry that presents a
+ risk of crashes when the index is read.
+
+
+
+
+
+ Avoid useless double decompression of GiST index entries
+ in contrib/intarray (Konstantin Knizhnik,
+ Matthias van de Meent, Tom Lane)
+
+
+
+
+
+ Fix contrib/pageinspect's
+ gist_page_items() function to work when there
+ are included index columns (Alexander Lakhin, Michael Paquier)
+
+
+ Previously, if the index has included
+ columns, gist_page_items() would fail to
+ display those values on index leaf pages, or crash outright on
+ non-leaf pages.
+
+
+
+
+
+ Fix
pg_dump to correctly handle new-style
+ SQL-language functions whose bodies require parse-time dependencies
+ on unique indexes (Tom Lane)
+
+
+ Such cases can arise from GROUP BY
+ and ON CONFLICT clauses, for example. The
+ function must then be postponed until after the unique index in the
+ dump output, but
pg_dump did not do that
+ and instead printed a warning about could not resolve
+ dependency loop.
+
+
+
+
+
+ Ensure
+ that pg_index.indisreplident
+ is kept up-to-date in relation cache entries (Shruthi Gowda)
+
+
+ This value could be stale in some cases. There is no core code that
+ relies on the relation cache's copy, so this is only a latent bug as
+ far as Postgres itself is concerned; but there may be extensions for
+ which it is a live bug.
+
+
+
+
+
+
+
+
Release 14.8
projects / postgresql.git / commitdiff