- Prevent possible data loss from concurrent truncations of SLRU logs
- (Noah Misch)
-
-
- This rare problem would manifest in later apparent
- wraparound or could not access status of
- transaction errors.
-
-
-
-
-
- Avoid unnecessary recursion to partitions in ALTER TABLE
- SET NOT NULL, when the target column is already
- marked NOT NULL (Tom Lane)
-
-
- This avoids a potential deadlock in
-
-
-
-
-
- Fix handling of expressions in CREATE TABLE LIKE
- with inheritance (Tom Lane)
-
-
- If a CREATE TABLE command uses
- both LIKE and traditional inheritance, column
- references in CHECK constraints and expression
- indexes that came from a LIKE parent table tended
- to get mis-numbered, resulting in wrong answers and/or bizarre error
- messages. The same could happen in GENERATED
- expressions, in branches that have that feature.
-
-
-
-
-
- Disallow DROP INDEX CONCURRENTLY on a partitioned
- table (Álvaro Herrera, Michael Paquier)
-
-
- This case failed anyway, but with a confusing error message.
-
-
-
-
-
- Recheck default partition constraints while routing an inserted or
- updated tuple to the correct partition (Amit Langote,
- Álvaro Herrera)
-
-
- This fixes race conditions when partitions are added concurrently
- with the insertion.
-
-
-
-
-
- Fix cache lookup failed for relation 0
- failures in logical replication workers (Tom Lane)
-
-
- The real-world impact is small, since the failure is unlikely, and
- if it does happen the worker would just exit and be restarted.
-
-
-
-
-
- Prevent logical replication workers from sending redundant ping
- requests (Tom Lane)
-
-
-
-
-
- During smart
shutdown, don't terminate background
- processes until all client (foreground) sessions are done (Tom Lane)
-
-
- The previous behavior broke parallel query processing, since the
- postmaster would terminate parallel workers and refuse to launch any
- new ones. It also caused autovacuum to cease functioning, which
- could have dire long-term effects if the surviving client sessions
- make a lot of data changes.
-
-
-
-
-
- Avoid recursive consumption of stack space while processing signals
- in the postmaster (Tom Lane)
-
-
- Heavy use of parallel processing has been observed to cause
- postmaster crashes due to too many concurrent signals requesting
- creation of a parallel worker process.
-
-
-
-
-
- Avoid running atexit handlers when exiting
- due to SIGQUIT (Kyotaro Horiguchi, Tom Lane)
-
-
- Most server processes followed this practice already, but the
- archiver process was overlooked. Backends that were still waiting
- for a client startup packet got it wrong, too.
-
-
-
-
-
- Avoid misoptimization of subquery qualifications that reference
- apparently-constant grouping columns (Tom Lane)
-
-
- A constant
subquery output column isn't really
- constant if it is a grouping column that appears in only some of the
- grouping sets.
-
-
-
-
-
- Avoid failure when SQL function inlining changes the shape of a
- potentially-hashable subplan comparison expression (Tom Lane)
-
-
-
-
-
- While building or re-building an index, tolerate the appearance of
- new HOT chains due to concurrent updates
- (Anastasia Lubennikova, Álvaro Herrera)
-
-
- This oversight could lead to failed to find parent tuple for
- heap-only tuple errors.
-
-
-
-
-
- Fix failure of parallel B-tree index scans when the index condition
- is unsatisfiable (James Hunter)
-
-
-
-
-
- Handle concurrent desummarization correctly during BRIN index scans
- (Alexander Lakhin, Álvaro Herrera)
-
-
- Previously, if a page range was desummarized at just the wrong time,
- an index scan might falsely raise an error indicating index
- corruption.
-
-
-
-
-
- Fix rare lost saved point in index
errors in scans of
- multicolumn GIN indexes (Tom Lane)
-
-
-
-
-
- Fix use-after-free hazard when an event trigger monitors
- an ALTER TABLE operation (Jehan-Guillaume de
- Rorthais)
-
-
-
-
-
Avoid failures when a BEFORE ROW UPDATE trigger
- returns the old
row of a table
- having missing
attributes (Amit Langote)
+ returns the old
row of a table having dropped
+ or missing
columns (Amit Langote, Tom Lane)
- This method of suppressing an update could result in unexpected
- CHECK constraint failures or
- incorrect RETURNING output, because
- the missing
columns would read as NULLs for those
+ This method of suppressing an update could result in crashes,
+ unexpected CHECK constraint failures, or
+ incorrect RETURNING output,
+ because missing
columns would read as NULLs for those
purposes. (A column is missing
for this purpose if
it was added by ALTER TABLE ADD COLUMN with a
- non-NULL, but constant, default value.)
+ non-NULL, but constant, default value.) Dropped columns could cause
+ trouble as well.
- Fix incorrect error message about inconsistent moving-aggregate
- data types (Jeff Janes)
-
-
-
-
-
- Avoid lockup when a parallel worker reports a very long error
- message (Vignesh C)
-
-
-
-
-
- Make
libpq support arbitrary-length lines
- in .pgpass files (Tom Lane)
-
-
- This is mostly useful to allow using very long security tokens as
- passwords.
-
-
-
-
-
Fix
ecpg's mis-processing
- Ensure that parallel
pg_restore processes
- foreign keys referencing partitioned tables in the correct order
- (Álvaro Herrera)
-
-
- Previously, it might try to restore a foreign key constraint before
- the required indexes were all in place, leading to an error.
-
-
-
-
-
- Use return not exit() in
- test programs (Peter Eisentraut)
-
-
- This avoids failures with pickier compilers.
-
-
-
-
-
projects / postgresql.git / commitdiff