PostgreSQL 9.6.20 release changes

• Same change PostgreSQL 13.1 · Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries
• Same change PostgreSQL 12.5 · Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries
• Same change PostgreSQL 11.10 · Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries
• Same change PostgreSQL 10.15 · Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries
• Same change PostgreSQL 9.5.24 · Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 13.1 · Fix usage of complex connection-string parameters in pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb
• Same change PostgreSQL 12.5 · Fix usage of complex connection-string parameters in pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb
• Same change PostgreSQL 11.10 · Fix usage of complex connection-string parameters in pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb
• Same change PostgreSQL 10.15 · Fix usage of complex connection-string parameters in pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb
• Same change PostgreSQL 9.5.24 · Fix usage of complex connection-string parameters in pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 13.1 · When psql's \connect command re-uses connection parameters, ensure that all non-overridden parameters from a previous connection string are re-used
• Same change PostgreSQL 12.5 · When psql's \connect command re-uses connection parameters, ensure that all non-overridden parameters from a previous connection string are re-used
• Same change PostgreSQL 11.10 · When psql's \connect command re-uses connection parameters, ensure that all non-overridden parameters from a previous connection string are re-used
• Same change PostgreSQL 10.15 · When psql's \connect command re-uses connection parameters, ensure that all non-overridden parameters from a previous connection string are re-used
• Same change PostgreSQL 9.5.24 · When psql's \connect command re-uses connection parameters, ensure that all non-overridden parameters from a previous connection string are re-used

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 13.1 · Prevent psql's \gset command from modifying specially-treated variables
• Same change PostgreSQL 12.5 · Prevent psql's \gset command from modifying specially-treated variables
• Same change PostgreSQL 11.10 · Prevent psql's \gset command from modifying specially-treated variables
• Same change PostgreSQL 10.15 · Prevent psql's \gset command from modifying specially-treated variables
• Same change PostgreSQL 9.5.24 · Prevent psql's \gset command from modifying specially-treated variables

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 12.5 · Prevent possible data loss from concurrent truncations of SLRU logs
• Same change PostgreSQL 11.10 · Prevent possible data loss from concurrent truncations of SLRU logs
• Same change PostgreSQL 10.15 · Prevent possible data loss from concurrent truncations of SLRU logs
• Same change PostgreSQL 9.5.24 · Prevent possible data loss from concurrent truncations of SLRU logs

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 13.1 · Ensure that SLRU directories are properly fsync'd during checkpoints
• Same change PostgreSQL 12.5 · Ensure that SLRU directories are properly fsync'd during checkpoints
• Same change PostgreSQL 11.10 · Ensure that SLRU directories are properly fsync'd during checkpoints
• Same change PostgreSQL 10.15 · Ensure that SLRU directories are properly fsync'd during checkpoints
• Same change PostgreSQL 9.5.24 · Ensure that SLRU directories are properly fsync'd during checkpoints

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 13.1 · Fix ALTER ROLE for users with the BYPASSRLS attribute
• Same change PostgreSQL 12.5 · Fix ALTER ROLE for users with the BYPASSRLS attribute
• Same change PostgreSQL 11.10 · Fix ALTER ROLE for users with the BYPASSRLS attribute
• Same change PostgreSQL 10.15 · Fix ALTER ROLE for users with the BYPASSRLS attribute
• Same change PostgreSQL 9.5.24 · Fix ALTER ROLE for users with the BYPASSRLS attribute

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 12.5 · Fix handling of expressions in CREATE TABLE LIKE with inheritance
• Same change PostgreSQL 11.10 · Fix handling of expressions in CREATE TABLE LIKE with inheritance
• Same change PostgreSQL 10.15 · Fix handling of expressions in CREATE TABLE LIKE with inheritance
• Same change PostgreSQL 9.5.24 · Fix handling of expressions in CREATE TABLE LIKE with inheritance

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 13.1 · Fix off-by-one conversion of negative years to BC dates in to_date() and to_timestamp()
• Same change PostgreSQL 12.5 · Fix off-by-one conversion of negative years to BC dates in to_date() and to_timestamp()
• Same change PostgreSQL 11.10 · Fix off-by-one conversion of negative years to BC dates in to_date() and to_timestamp()
• Same change PostgreSQL 10.15 · Fix off-by-one conversion of negative years to BC dates in to_date() and to_timestamp()
• Same change PostgreSQL 9.5.24 · Fix off-by-one conversion of negative years to BC dates in to_date() and to_timestamp()

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 13.1 · Ensure that standby servers will archive WAL timeline history files when archive_mode is set to always
• Same change PostgreSQL 12.5 · Ensure that standby servers will archive WAL timeline history files when archive_mode is set to always
• Same change PostgreSQL 11.10 · Ensure that standby servers will archive WAL timeline history files when archive_mode is set to always
• Same change PostgreSQL 10.15 · Ensure that standby servers will archive WAL timeline history files when archive_mode is set to always
• Same change PostgreSQL 9.5.24 · Ensure that standby servers will archive WAL timeline history files when archive_mode is set to always

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 12.5 · During “smart” shutdown, don't terminate background processes until all client (foreground) sessions are done
• Same change PostgreSQL 11.10 · During “smart” shutdown, don't terminate background processes until all client (foreground) sessions are done
• Same change PostgreSQL 10.15 · During “smart” shutdown, don't terminate background processes until all client (foreground) sessions are done

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 12.5 · Avoid recursive consumption of stack space while processing signals in the postmaster
• Same change PostgreSQL 11.10 · Avoid recursive consumption of stack space while processing signals in the postmaster
• Same change PostgreSQL 10.15 · Avoid recursive consumption of stack space while processing signals in the postmaster

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 12.5 · Avoid running atexit handlers when exiting due to SIGQUIT
• Same change PostgreSQL 11.10 · Avoid running atexit handlers when exiting due to SIGQUIT
• Same change PostgreSQL 10.15 · Avoid running atexit handlers when exiting due to SIGQUIT
• Same change PostgreSQL 9.5.24 · Avoid running atexit handlers when exiting due to SIGQUIT

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 12.5 · Avoid misoptimization of subquery qualifications that reference apparently-constant grouping columns
• Same change PostgreSQL 11.10 · Avoid misoptimization of subquery qualifications that reference apparently-constant grouping columns
• Same change PostgreSQL 10.15 · Avoid misoptimization of subquery qualifications that reference apparently-constant grouping columns
• Same change PostgreSQL 9.5.24 · Avoid misoptimization of subquery qualifications that reference apparently-constant grouping columns

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 12.5 · Avoid failure when SQL function inlining changes the shape of a potentially-hashable subplan comparison expression
• Same change PostgreSQL 11.10 · Avoid failure when SQL function inlining changes the shape of a potentially-hashable subplan comparison expression
• Same change PostgreSQL 10.15 · Avoid failure when SQL function inlining changes the shape of a potentially-hashable subplan comparison expression
• Same change PostgreSQL 9.5.24 · Avoid failure when SQL function inlining changes the shape of a potentially-hashable subplan comparison expression

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 12.5 · While building or re-building an index, tolerate the appearance of new HOT chains due to concurrent updates
• Same change PostgreSQL 11.10 · While building or re-building an index, tolerate the appearance of new HOT chains due to concurrent updates
• Same change PostgreSQL 10.15 · While building or re-building an index, tolerate the appearance of new HOT chains due to concurrent updates
• Same change PostgreSQL 9.5.24 · While building or re-building an index, tolerate the appearance of new HOT chains due to concurrent updates

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 13.1 · Ensure that data is detoasted before being inserted into a BRIN index
• Same change PostgreSQL 12.5 · Ensure that data is detoasted before being inserted into a BRIN index
• Same change PostgreSQL 11.10 · Ensure that data is detoasted before being inserted into a BRIN index
• Same change PostgreSQL 10.15 · Ensure that data is detoasted before being inserted into a BRIN index
• Same change PostgreSQL 9.5.24 · Ensure that data is detoasted before being inserted into a BRIN index

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 12.5 · Handle concurrent desummarization correctly during BRIN index scans
• Same change PostgreSQL 11.10 · Handle concurrent desummarization correctly during BRIN index scans
• Same change PostgreSQL 10.15 · Handle concurrent desummarization correctly during BRIN index scans
• Same change PostgreSQL 9.5.24 · Handle concurrent desummarization correctly during BRIN index scans

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 12.5 · Fix rare “lost saved point in index” errors in scans of multicolumn GIN indexes
• Same change PostgreSQL 11.10 · Fix rare “lost saved point in index” errors in scans of multicolumn GIN indexes
• Same change PostgreSQL 10.15 · Fix rare “lost saved point in index” errors in scans of multicolumn GIN indexes
• Same change PostgreSQL 9.5.24 · Fix rare "lost saved point in index" errors in scans of multicolumn GIN indexes

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 12.5 · Fix use-after-free hazard when an event trigger monitors an ALTER TABLE operation
• Same change PostgreSQL 11.10 · Fix use-after-free hazard when an event trigger monitors an ALTER TABLE operation
• Same change PostgreSQL 10.15 · Fix use-after-free hazard when an event trigger monitors an ALTER TABLE operation
• Same change PostgreSQL 9.5.24 · Fix use-after-free hazard when an event trigger monitors an ALTER TABLE operation

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 12.5 · Fix incorrect error message about inconsistent moving-aggregate data types
• Same change PostgreSQL 11.10 · Fix incorrect error message about inconsistent moving-aggregate data types
• Same change PostgreSQL 10.15 · Fix incorrect error message about inconsistent moving-aggregate data types
• Same change PostgreSQL 9.5.24 · Fix incorrect error message about inconsistent moving-aggregate data types

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 12.5 · Avoid lockup when a parallel worker reports a very long error message
• Same change PostgreSQL 11.10 · Avoid lockup when a parallel worker reports a very long error message
• Same change PostgreSQL 10.15 · Avoid lockup when a parallel worker reports a very long error message
• Same change PostgreSQL 9.5.24 · Avoid lockup when a parallel worker reports a very long error message

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 13.1 · Avoid unnecessary failure when transferring very large payloads through shared memory queues
• Same change PostgreSQL 12.5 · Avoid unnecessary failure when transferring very large payloads through shared memory queues
• Same change PostgreSQL 11.10 · Avoid unnecessary failure when transferring very large payloads through shared memory queues
• Same change PostgreSQL 10.15 · Avoid unnecessary failure when transferring very large payloads through shared memory queues
• Same change PostgreSQL 9.5.24 · Avoid unnecessary failure when transferring very large payloads through shared memory queues

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 13.1 · Fix relation cache memory leaks with RLS policies
• Same change PostgreSQL 12.5 · Fix relation cache memory leaks with RLS policies
• Same change PostgreSQL 11.10 · Fix relation cache memory leaks with RLS policies
• Same change PostgreSQL 10.15 · Fix relation cache memory leaks with RLS policies
• Same change PostgreSQL 9.5.24 · Fix relation cache memory leaks with RLS policies

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 13.1 · Fix small memory leak when SIGHUP processing decides that a new GUC variable value cannot be applied without a restart
• Same change PostgreSQL 12.5 · Fix small memory leak when SIGHUP processing decides that a new GUC variable value cannot be applied without a restart
• Same change PostgreSQL 11.10 · Fix small memory leak when SIGHUP processing decides that a new GUC variable value cannot be applied without a restart
• Same change PostgreSQL 10.15 · Fix small memory leak when SIGHUP processing decides that a new GUC variable value cannot be applied without a restart
• Same change PostgreSQL 9.5.24 · Fix small memory leak when SIGHUP processing decides that a new GUC variable value cannot be applied without a restart

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 12.5 · Make libpq support arbitrary-length lines in .pgpass files
• Same change PostgreSQL 11.10 · Make libpq support arbitrary-length lines in .pgpass files
• Same change PostgreSQL 10.15 · Make libpq support arbitrary-length lines in .pgpass files
• Same change PostgreSQL 9.5.24 · Make libpq support arbitrary-length lines in .pgpass files

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 13.1 · In libpq for Windows, call WSAStartup() once per process and WSACleanup() not at all
• Same change PostgreSQL 12.5 · In libpq for Windows, call WSAStartup() once per process and WSACleanup() not at all
• Same change PostgreSQL 11.10 · In libpq for Windows, call WSAStartup() once per process and WSACleanup() not at all
• Same change PostgreSQL 10.15 · In libpq for Windows, call WSAStartup() once per process and WSACleanup() not at all
• Same change PostgreSQL 9.5.24 · In libpq for Windows, call WSAStartup() once per process and WSACleanup() not at all

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 13.1 · Fix ecpg library's per-thread initialization logic for Windows
• Same change PostgreSQL 12.5 · Fix ecpg library's per-thread initialization logic for Windows
• Same change PostgreSQL 11.10 · Fix ecpg library's per-thread initialization logic for Windows
• Same change PostgreSQL 10.15 · Fix ecpg library's per-thread initialization logic for Windows
• Same change PostgreSQL 9.5.24 · Fix ecpg library's per-thread initialization logic for Windows

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 13.1 · On Windows, make psql read the output of a backtick command in text mode, not binary mode
• Same change PostgreSQL 12.5 · On Windows, make psql read the output of a backtick command in text mode, not binary mode
• Same change PostgreSQL 11.10 · On Windows, make psql read the output of a backtick command in text mode, not binary mode
• Same change PostgreSQL 10.15 · On Windows, make psql read the output of a backtick command in text mode, not binary mode
• Same change PostgreSQL 9.5.24 · On Windows, make psql read the output of a backtick command in text mode, not binary mode

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 13.1 · Ensure that pg_dump collects per-column information about extension configuration tables
• Same change PostgreSQL 12.5 · Ensure that pg_dump collects per-column information about extension configuration tables
• Same change PostgreSQL 11.10 · Ensure that pg_dump collects per-column information about extension configuration tables
• Same change PostgreSQL 10.15 · Ensure that pg_dump collects per-column information about extension configuration tables
• Same change PostgreSQL 9.5.24 · Ensure that pg_dump collects per-column information about extension configuration tables

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 13.1 · Make pg_upgrade check for pre-existence of tablespace directories in the target cluster
• Same change PostgreSQL 12.5 · Make pg_upgrade check for pre-existence of tablespace directories in the target cluster
• Same change PostgreSQL 11.10 · Make pg_upgrade check for pre-existence of tablespace directories in the target cluster
• Same change PostgreSQL 10.15 · Make pg_upgrade check for pre-existence of tablespace directories in the target cluster
• Same change PostgreSQL 9.5.24 · Make pg_upgrade check for pre-existence of tablespace directories in the target cluster

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 13.1 · Fix potential memory leak in contrib/pgcrypto
• Same change PostgreSQL 12.5 · Fix potential memory leak in contrib/pgcrypto
• Same change PostgreSQL 11.10 · Fix potential memory leak in contrib/pgcrypto
• Same change PostgreSQL 10.15 · Fix potential memory leak in contrib/pgcrypto
• Same change PostgreSQL 9.5.24 · Fix potential memory leak in contrib/pgcrypto

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 13.1 · Add check for an unlikely failure case in contrib/pgcrypto
• Same change PostgreSQL 12.5 · Add check for an unlikely failure case in contrib/pgcrypto
• Same change PostgreSQL 11.10 · Add check for an unlikely failure case in contrib/pgcrypto
• Same change PostgreSQL 10.15 · Add check for an unlikely failure case in contrib/pgcrypto
• Same change PostgreSQL 9.5.24 · Add check for an unlikely failure case in contrib/pgcrypto

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.5.24 · Use return not exit() in configure's test programs

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 13.1 · Update time zone data files to tzdata release 2020d for DST law changes in Fiji, Morocco, Palestine, the Canadian Yukon, Macquarie Island, and Casey Station (Antarctica); plus historical corrections for France, Hungary, Monaco, and Palestine.
• Same change PostgreSQL 12.5 · Update time zone data files to tzdata release 2020d for DST law changes in Fiji, Morocco, Palestine, the Canadian Yukon, Macquarie Island, and Casey Station (Antarctica); plus historical corrections for France, Hungary, Monaco, and Palestine.
• Same change PostgreSQL 11.10 · Update time zone data files to tzdata release 2020d for DST law changes in Fiji, Morocco, Palestine, the Canadian Yukon, Macquarie Island, and Casey Station (Antarctica); plus historical corrections for France, Hungary, Monaco, and Palestine.
• Same change PostgreSQL 10.15 · Update time zone data files to tzdata release 2020d for DST law changes in Fiji, Morocco, Palestine, the Canadian Yukon, Macquarie Island, and Casey Station (Antarctica); plus historical corrections for France, Hungary, Monaco, and Palestine.
• Same change PostgreSQL 9.5.24 · Update time zone data files to tzdata release 2020d for DST law changes in Fiji, Morocco, Palestine, the Canadian Yukon, Macquarie Island, and Casey Station (Antarctica); plus historical corrections for France, Hungary, Monaco, and Palestine.

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 13.1 · Sync our copy of the timezone library with IANA tzcode release 2020d
• Same change PostgreSQL 12.5 · Sync our copy of the timezone library with IANA tzcode release 2020d
• Same change PostgreSQL 11.10 · Sync our copy of the timezone library with IANA tzcode release 2020d
• Same change PostgreSQL 10.15 · Sync our copy of the timezone library with IANA tzcode release 2020d
• Same change PostgreSQL 9.5.24 · Sync our copy of the timezone library with IANA tzcode release 2020d

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.