PostgreSQL 9.4.26 release changes

• Same change PostgreSQL 12.2 · Avoid failure in logical decoding when a large transaction must be spilled into many separate temporary files
• Same change PostgreSQL 11.7 · Avoid failure in logical decoding when a large transaction must be spilled into many separate temporary files
• Same change PostgreSQL 10.12 · Avoid failure in logical decoding when a large transaction must be spilled into many separate temporary files
• Same change PostgreSQL 9.6.17 · Avoid failure in logical decoding when a large transaction must be spilled into many separate temporary files
• Same change PostgreSQL 9.5.21 · Avoid failure in logical decoding when a large transaction must be spilled into many separate temporary 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 12.2 · Fix failure in logical replication publisher after a database crash and restart
• Same change PostgreSQL 11.7 · Fix failure in logical replication publisher after a database crash and restart
• Same change PostgreSQL 10.12 · Fix failure in logical replication publisher after a database crash and restart
• Same change PostgreSQL 9.6.17 · Fix failure in logical replication publisher after a database crash and restart
• Same change PostgreSQL 9.5.21 · Fix failure in logical replication publisher after a database crash and 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.2 · Avoid memory leak when there are no free dynamic shared memory slots
• Same change PostgreSQL 11.7 · Avoid memory leak when there are no free dynamic shared memory slots
• Same change PostgreSQL 10.12 · Avoid memory leak when there are no free dynamic shared memory slots
• Same change PostgreSQL 9.6.17 · Avoid memory leak when there are no free dynamic shared memory slots
• Same change PostgreSQL 9.5.21 · Avoid memory leak when there are no free dynamic shared memory slots

“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.2 · Ignore the CONCURRENTLY option when performing an index creation, drop, or rebuild on a temporary table
• Same change PostgreSQL 11.7 · Ignore the CONCURRENTLY option when performing an index creation, drop, or rebuild on a temporary table
• Same change PostgreSQL 10.12 · Ignore the CONCURRENTLY option when performing an index creation, drop, or rebuild on a temporary table
• Same change PostgreSQL 9.6.17 · Ignore the CONCURRENTLY option when performing an index creation, drop, or rebuild on a temporary table
• Same change PostgreSQL 9.5.21 · Ignore the CONCURRENTLY option when performing an index creation, drop, or rebuild on a temporary table

“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.2 · Fix possible failure when resetting expression indexes on temporary tables that are marked ON COMMIT DELETE ROWS
• Same change PostgreSQL 11.7 · Fix possible failure when resetting expression indexes on temporary tables that are marked ON COMMIT DELETE ROWS
• Same change PostgreSQL 10.12 · Fix possible failure when resetting expression indexes on temporary tables that are marked ON COMMIT DELETE ROWS
• Same change PostgreSQL 9.6.17 · Fix possible failure when resetting expression indexes on temporary tables that are marked ON COMMIT DELETE ROWS
• Same change PostgreSQL 9.5.21 · Fix possible failure when resetting expression indexes on temporary tables that are marked ON COMMIT DELETE ROWS

“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.2 · Fix handling of deleted pages in GIN indexes
• Same change PostgreSQL 11.7 · Fix handling of deleted pages in GIN indexes
• Same change PostgreSQL 10.12 · Fix handling of deleted pages in GIN indexes
• Same change PostgreSQL 9.6.17 · Fix handling of deleted pages in GIN indexes
• Same change PostgreSQL 9.5.21 · Fix handling of deleted pages in 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.2 · Fix possible crash with a SubPlan (sub-SELECT) within a multi-row VALUES list
• Same change PostgreSQL 11.7 · Fix possible crash with a SubPlan (sub-SELECT) within a multi-row VALUES list
• Same change PostgreSQL 10.12 · Fix possible crash with a SubPlan (sub-SELECT) within a multi-row VALUES list
• Same change PostgreSQL 9.6.17 · Fix possible crash with a SubPlan (sub-SELECT) within a multi-row VALUES list
• Same change PostgreSQL 9.5.21 · Fix possible crash with a SubPlan (sub-SELECT) within a multi-row VALUES list

“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.2 · Fix unlikely crash with pass-by-reference aggregate transition states
• Same change PostgreSQL 11.7 · Fix unlikely crash with pass-by-reference aggregate transition states
• Same change PostgreSQL 10.12 · Fix unlikely crash with pass-by-reference aggregate transition states
• Same change PostgreSQL 9.6.17 · Fix unlikely crash with pass-by-reference aggregate transition states
• Same change PostgreSQL 9.5.21 · Fix unlikely crash with pass-by-reference aggregate transition states

“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.2 · Improve error reporting in to_date() and to_timestamp()
• Same change PostgreSQL 11.7 · Improve error reporting in to_date() and to_timestamp()
• Same change PostgreSQL 10.12 · Improve error reporting in to_date() and to_timestamp()
• Same change PostgreSQL 9.6.17 · Improve error reporting in to_date() and to_timestamp()
• Same change PostgreSQL 9.5.21 · Improve error reporting 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 12.2 · Fix off-by-one result for EXTRACT(ISOYEAR FROM timestamp) for BC dates
• Same change PostgreSQL 11.7 · Fix off-by-one result for EXTRACT(ISOYEAR FROM timestamp) for BC dates
• Same change PostgreSQL 10.12 · Fix off-by-one result for EXTRACT(ISOYEAR FROM timestamp) for BC dates
• Same change PostgreSQL 9.6.17 · Fix off-by-one result for EXTRACT(ISOYEAR FROM timestamp) for BC dates
• Same change PostgreSQL 9.5.21 · Fix off-by-one result for EXTRACT(ISOYEAR FROM timestamp) for BC dates

“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.2 · Avoid stack overflow in information_schema views when a self-referential view exists in the system catalogs
• Same change PostgreSQL 11.7 · Avoid stack overflow in information_schema views when a self-referential view exists in the system catalogs
• Same change PostgreSQL 10.12 · Avoid stack overflow in information_schema views when a self-referential view exists in the system catalogs
• Same change PostgreSQL 9.6.17 · Avoid stack overflow in information_schema views when a self-referential view exists in the system catalogs
• Same change PostgreSQL 9.5.21 · Avoid stack overflow in information_schema views when a self-referential view exists in the system catalogs

“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.2 · Improve performance of hash joins with very large inner relations
• Same change PostgreSQL 11.7 · Improve performance of hash joins with very large inner relations
• Same change PostgreSQL 10.12 · Improve performance of hash joins with very large inner relations
• Same change PostgreSQL 9.6.17 · Improve performance of hash joins with very large inner relations
• Same change PostgreSQL 9.5.21 · Improve performance of hash joins with very large inner relations

“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.2 · Fix edge-case crashes and misestimations in selectivity calculations for the <@ and @> range operators
• Same change PostgreSQL 11.7 · Fix edge-case crashes and misestimations in selectivity calculations for the <@ and @> range operators
• Same change PostgreSQL 10.12 · Fix edge-case crashes and misestimations in selectivity calculations for the <@ and @> range operators
• Same change PostgreSQL 9.6.17 · Fix edge-case crashes and misestimations in selectivity calculations for the <@ and @> range operators
• Same change PostgreSQL 9.5.21 · Fix edge-case crashes and misestimations in selectivity calculations for the <@ and @> range operators

“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.2 · Improve error reporting for attempts to use automatic updating of views with conditional INSTEAD rules
• Same change PostgreSQL 11.7 · Improve error reporting for attempts to use automatic updating of views with conditional INSTEAD rules
• Same change PostgreSQL 10.12 · Improve error reporting for attempts to use automatic updating of views with conditional INSTEAD rules
• Same change PostgreSQL 9.6.17 · Improve error reporting for attempts to use automatic updating of views with conditional INSTEAD rules
• Same change PostgreSQL 9.5.21 · Improve error reporting for attempts to use automatic updating of views with conditional INSTEAD rules

“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.2 · Prevent a composite type from being included in itself indirectly via a range type
• Same change PostgreSQL 11.7 · Prevent a composite type from being included in itself indirectly via a range type
• Same change PostgreSQL 10.12 · Prevent a composite type from being included in itself indirectly via a range type
• Same change PostgreSQL 9.6.17 · Prevent a composite type from being included in itself indirectly via a range type
• Same change PostgreSQL 9.5.21 · Prevent a composite type from being included in itself indirectly via a range type

“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.2 · Fix error reporting for index expressions of prohibited types
• Same change PostgreSQL 11.7 · Fix error reporting for index expressions of prohibited types
• Same change PostgreSQL 10.12 · Fix error reporting for index expressions of prohibited types
• Same change PostgreSQL 9.6.17 · Fix error reporting for index expressions of prohibited types
• Same change PostgreSQL 9.5.21 · Fix error reporting for index expressions of prohibited 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.2 · Fix dumping of views that contain only a VALUES list to handle cases where a view output column has been renamed
• Same change PostgreSQL 11.7 · Fix dumping of views that contain only a VALUES list to handle cases where a view output column has been renamed
• Same change PostgreSQL 10.12 · Fix dumping of views that contain only a VALUES list to handle cases where a view output column has been renamed
• Same change PostgreSQL 9.6.17 · Fix dumping of views that contain only a VALUES list to handle cases where a view output column has been renamed
• Same change PostgreSQL 9.5.21 · Fix dumping of views that contain only a VALUES list to handle cases where a view output column has been renamed

“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.2 · Allow libpq to parse all GSS-related connection parameters even when the GSSAPI code hasn't been compiled in
• Same change PostgreSQL 11.7 · Allow libpq to parse all GSS-related connection parameters even when the GSSAPI code hasn't been compiled in
• Same change PostgreSQL 10.12 · Allow libpq to parse all GSS-related connection parameters even when the GSSAPI code hasn't been compiled in
• Same change PostgreSQL 9.6.17 · Allow libpq to parse all GSS-related connection parameters even when the GSSAPI code hasn't been compiled in
• Same change PostgreSQL 9.5.21 · Allow libpq to parse all GSS-related connection parameters even when the GSSAPI code hasn't been compiled in

“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.2 · Fix incorrect handling of %b and %B format codes in ecpg's PGTYPEStimestamp_fmt_asc() function
• Same change PostgreSQL 11.7 · Fix incorrect handling of %b and %B format codes in ecpg's PGTYPEStimestamp_fmt_asc() function
• Same change PostgreSQL 10.12 · Fix incorrect handling of %b and %B format codes in ecpg's PGTYPEStimestamp_fmt_asc() function
• Same change PostgreSQL 9.6.17 · Fix incorrect handling of %b and %B format codes in ecpg's PGTYPEStimestamp_fmt_asc() function
• Same change PostgreSQL 9.5.21 · Fix incorrect handling of %b and %B format codes in ecpg's PGTYPEStimestamp_fmt_asc() function

“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.2 · Fix parallel pg_dump/pg_restore to more gracefully handle failure to create worker processes
• Same change PostgreSQL 11.7 · Fix parallel pg_dump/pg_restore to more gracefully handle failure to create worker processes
• Same change PostgreSQL 10.12 · Fix parallel pg_dump/pg_restore to more gracefully handle failure to create worker processes
• Same change PostgreSQL 9.6.17 · Fix parallel pg_dump/pg_restore to more gracefully handle failure to create worker processes
• Same change PostgreSQL 9.5.21 · Fix parallel pg_dump/pg_restore to more gracefully handle failure to create worker processes

“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.2 · Prevent possible crash or lockup when attempting to terminate a parallel pg_dump/pg_restore run via a signal
• Same change PostgreSQL 11.7 · Prevent possible crash or lockup when attempting to terminate a parallel pg_dump/pg_restore run via a signal
• Same change PostgreSQL 10.12 · Prevent possible crash or lockup when attempting to terminate a parallel pg_dump/pg_restore run via a signal
• Same change PostgreSQL 9.6.17 · Prevent possible crash or lockup when attempting to terminate a parallel pg_dump/pg_restore run via a signal
• Same change PostgreSQL 9.5.21 · Prevent possible crash or lockup when attempting to terminate a parallel pg_dump/pg_restore run via a signal

“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.2 · In pg_upgrade, look inside arrays and ranges while searching for non-upgradable data types in tables
• Same change PostgreSQL 11.7 · In pg_upgrade, look inside arrays and ranges while searching for non-upgradable data types in tables
• Same change PostgreSQL 10.12 · In pg_upgrade, look inside arrays and ranges while searching for non-upgradable data types in tables
• Same change PostgreSQL 9.6.17 · In pg_upgrade, look inside arrays and ranges while searching for non-upgradable data types in tables
• Same change PostgreSQL 9.5.21 · In pg_upgrade, look inside arrays and ranges while searching for non-upgradable data types in 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 12.2 · Apply more thorough syntax checking to createuser's --connection-limit option
• Same change PostgreSQL 11.7 · Apply more thorough syntax checking to createuser's --connection-limit option
• Same change PostgreSQL 10.12 · Apply more thorough syntax checking to createuser's --connection-limit option
• Same change PostgreSQL 9.6.17 · Apply more thorough syntax checking to createuser's --connection-limit option
• Same change PostgreSQL 9.5.21 · Apply more thorough syntax checking to createuser's --connection-limit option

“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.2 · In contrib/dict_int, reject maxlen settings less than one
• Same change PostgreSQL 11.7 · In contrib/dict_int, reject maxlen settings less than one
• Same change PostgreSQL 10.12 · In contrib/dict_int, reject maxlen settings less than one
• Same change PostgreSQL 9.6.17 · In contrib/dict_int, reject maxlen settings less than one
• Same change PostgreSQL 9.5.21 · In contrib/dict_int, reject maxlen settings less than one

“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.2 · Disallow NULL category values in contrib/tablefunc's crosstab() function
• Same change PostgreSQL 11.7 · Disallow NULL category values in contrib/tablefunc's crosstab() function
• Same change PostgreSQL 10.12 · Disallow NULL category values in contrib/tablefunc's crosstab() function
• Same change PostgreSQL 9.6.17 · Disallow NULL category values in contrib/tablefunc's crosstab() function
• Same change PostgreSQL 9.5.21 · Disallow NULL category values in contrib/tablefunc's crosstab() function

“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.2 · Mark some timeout and statistics-tracking GUC variables as PGDLLIMPORT, to allow extensions to access them on Windows
• Same change PostgreSQL 11.7 · Mark some timeout and statistics-tracking GUC variables as PGDLLIMPORT, to allow extensions to access them on Windows
• Same change PostgreSQL 10.12 · Mark some timeout and statistics-tracking GUC variables as PGDLLIMPORT, to allow extensions to access them on Windows
• Same change PostgreSQL 9.6.17 · Mark some timeout and statistics-tracking GUC variables as PGDLLIMPORT, to allow extensions to access them on Windows
• Same change PostgreSQL 9.5.21 · Mark some timeout and statistics-tracking GUC variables as PGDLLIMPORT, to allow extensions to access them on 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 12.2 · Fix race condition that led to delayed delivery of interprocess signals on Windows
• Same change PostgreSQL 11.7 · Fix race condition that led to delayed delivery of interprocess signals on Windows
• Same change PostgreSQL 10.12 · Fix race condition that led to delayed delivery of interprocess signals on Windows
• Same change PostgreSQL 9.6.17 · Fix race condition that led to delayed delivery of interprocess signals on Windows
• Same change PostgreSQL 9.5.21 · Fix race condition that led to delayed delivery of interprocess signals on 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 12.2 · On Windows, retry a few times after an ERROR_ACCESS_DENIED file access failure
• Same change PostgreSQL 11.7 · On Windows, retry a few times after an ERROR_ACCESS_DENIED file access failure
• Same change PostgreSQL 10.12 · On Windows, retry a few times after an ERROR_ACCESS_DENIED file access failure
• Same change PostgreSQL 9.6.17 · On Windows, retry a few times after an ERROR_ACCESS_DENIED file access failure
• Same change PostgreSQL 9.5.21 · On Windows, retry a few times after an ERROR_ACCESS_DENIED file access failure

“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.