PostgreSQL 9.4.11 release changes

• Same change PostgreSQL 9.6.2 · Fix a race condition that could cause indexes built with CREATE INDEX CONCURRENTLY to be corrupt
• Same change PostgreSQL 9.5.6 · Fix a race condition that could cause indexes built with CREATE INDEX CONCURRENTLY to be corrupt
• Same change PostgreSQL 9.3.16 · Fix a race condition that could cause indexes built with CREATE INDEX CONCURRENTLY to be corrupt
• Same change PostgreSQL 9.2.20 · Fix a race condition that could cause indexes built with CREATE INDEX CONCURRENTLY to be corrupt

“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.6.2 · Ensure that the special snapshot used for catalog scans is not invalidated by premature data pruning
• Same change PostgreSQL 9.5.6 · Ensure that the special snapshot used for catalog scans is not invalidated by premature data pruning

“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.6.2 · Unconditionally WAL-log creation of the "init fork" for an unlogged table
• Same change PostgreSQL 9.5.6 · Unconditionally WAL-log creation of the "init fork" for an unlogged table
• Same change PostgreSQL 9.3.16 · Unconditionally WAL-log creation of the "init fork" for an unlogged table
• Same change PostgreSQL 9.2.20 · Unconditionally WAL-log creation of the "init fork" for an unlogged 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 9.5.6 · Reduce interlocking on standby servers during the replay of btree index vacuuming operations

“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.6.2 · If the stats collector dies during hot standby, restart it
• Same change PostgreSQL 9.5.6 · If the stats collector dies during hot standby, restart it
• Same change PostgreSQL 9.3.16 · If the stats collector dies during hot standby, restart it
• Same change PostgreSQL 9.2.20 · If the stats collector dies during hot standby, restart it

“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.6.2 · Ensure that hot standby feedback works correctly when it's enabled at standby server start
• Same change PostgreSQL 9.5.6 · Ensure that hot standby feedback works correctly when it's enabled at standby server start
• Same change PostgreSQL 9.3.16 · Ensure that hot standby feedback works correctly when it's enabled at standby server start

“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.6.2 · Check for interrupts while hot standby is waiting for a conflicting query
• Same change PostgreSQL 9.5.6 · Check for interrupts while hot standby is waiting for a conflicting query
• Same change PostgreSQL 9.3.16 · Check for interrupts while hot standby is waiting for a conflicting query
• Same change PostgreSQL 9.2.20 · Check for interrupts while hot standby is waiting for a conflicting query

“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.6.2 · Avoid constantly respawning the autovacuum launcher in a corner case
• Same change PostgreSQL 9.5.6 · Avoid constantly respawning the autovacuum launcher in a corner case
• Same change PostgreSQL 9.3.16 · Avoid constantly respawning the autovacuum launcher in a corner case
• Same change PostgreSQL 9.2.20 · Avoid constantly respawning the autovacuum launcher in a corner case

“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.6.2 · Fix check for when an extension member object can be dropped
• Same change PostgreSQL 9.5.6 · Fix check for when an extension member object can be dropped
• Same change PostgreSQL 9.3.16 · Fix check for when an extension member object can be dropped
• Same change PostgreSQL 9.2.20 · Fix check for when an extension member object can be dropped

“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.6.2 · Make sure ALTER TABLE preserves index tablespace assignments when rebuilding indexes
• Same change PostgreSQL 9.5.6 · Make sure ALTER TABLE preserves index tablespace assignments when rebuilding indexes
• Same change PostgreSQL 9.3.16 · Make sure ALTER TABLE preserves index tablespace assignments when rebuilding indexes
• Same change PostgreSQL 9.2.20 · Make sure ALTER TABLE preserves index tablespace assignments when rebuilding 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 9.6.2 · Fix incorrect updating of trigger function properties when changing a foreign-key constraint's deferrability properties with ALTER TABLE ... ALTER CONSTRAINT
• Same change PostgreSQL 9.5.6 · Fix incorrect updating of trigger function properties when changing a foreign-key constraint's deferrability properties with ALTER TABLE ... ALTER CONSTRAINT

“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.6.2 · Prevent dropping a foreign-key constraint if there are pending trigger events for the referenced relation
• Same change PostgreSQL 9.5.6 · Prevent dropping a foreign-key constraint if there are pending trigger events for the referenced relation
• Same change PostgreSQL 9.3.16 · Prevent dropping a foreign-key constraint if there are pending trigger events for the referenced relation
• Same change PostgreSQL 9.2.20 · Prevent dropping a foreign-key constraint if there are pending trigger events for the referenced relation

“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.6.2 · Fix processing of OID column when a table with OIDs is associated to a parent with OIDs via ALTER TABLE ... INHERIT
• Same change PostgreSQL 9.5.6 · Fix processing of OID column when a table with OIDs is associated to a parent with OIDs via ALTER TABLE ... INHERIT
• Same change PostgreSQL 9.3.16 · Fix processing of OID column when a table with OIDs is associated to a parent with OIDs via ALTER TABLE ... INHERIT
• Same change PostgreSQL 9.2.20 · Fix processing of OID column when a table with OIDs is associated to a parent with OIDs via ALTER TABLE ... INHERIT

“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.6.2 · Fix CREATE OR REPLACE VIEW to update the view query before attempting to apply the new view options
• Same change PostgreSQL 9.5.6 · Fix CREATE OR REPLACE VIEW to update the view query before attempting to apply the new view options

“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.6.2 · Report correct object identity during ALTER TEXT SEARCH CONFIGURATION
• Same change PostgreSQL 9.5.6 · Report correct object identity during ALTER TEXT SEARCH CONFIGURATION
• Same change PostgreSQL 9.3.16 · Report correct object identity during ALTER TEXT SEARCH CONFIGURATION

“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.6 · Check for serializability conflicts before reporting constraint-violation failures
• Same change PostgreSQL 9.3.16 · Check for serializability conflicts before reporting constraint-violation failures
• Same change PostgreSQL 9.2.20 · Check for serializability conflicts before reporting constraint-violation failures

“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.6.2 · Prevent multicolumn expansion of foo.* in an UPDATE source expression
• Same change PostgreSQL 9.5.6 · Prevent multicolumn expansion of foo.* in an UPDATE source expression
• Same change PostgreSQL 9.3.16 · Prevent multicolumn expansion of foo.* in an UPDATE source 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 9.6.2 · Ensure that column typmods are determined accurately for multi-row VALUES constructs
• Same change PostgreSQL 9.5.6 · Ensure that column typmods are determined accurately for multi-row VALUES constructs
• Same change PostgreSQL 9.3.16 · Ensure that column typmods are determined accurately for multi-row VALUES constructs
• Same change PostgreSQL 9.2.20 · Ensure that column typmods are determined accurately for multi-row VALUES constructs

“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.6.2 · Throw error for an unfinished Unicode surrogate pair at the end of a Unicode string
• Same change PostgreSQL 9.5.6 · Throw error for an unfinished Unicode surrogate pair at the end of a Unicode string
• Same change PostgreSQL 9.3.16 · Throw error for an unfinished Unicode surrogate pair at the end of a Unicode string
• Same change PostgreSQL 9.2.20 · Throw error for an unfinished Unicode surrogate pair at the end of a Unicode string

“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.6.2 · Ensure that a purely negative text search query, such as !foo, matches empty tsvectors
• Same change PostgreSQL 9.5.6 · Ensure that a purely negative text search query, such as !foo, matches empty tsvectors
• Same change PostgreSQL 9.3.16 · Ensure that a purely negative text search query, such as !foo, matches empty tsvectors
• Same change PostgreSQL 9.2.20 · Ensure that a purely negative text search query, such as !foo, matches empty tsvectors

“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.6.2 · Prevent crash when ts_rewrite() replaces a non-top-level subtree with an empty query
• Same change PostgreSQL 9.5.6 · Prevent crash when ts_rewrite() replaces a non-top-level subtree with an empty query
• Same change PostgreSQL 9.3.16 · Prevent crash when ts_rewrite() replaces a non-top-level subtree with an empty query
• Same change PostgreSQL 9.2.20 · Prevent crash when ts_rewrite() replaces a non-top-level subtree with an empty query

“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.6.2 · Fix performance problems in ts_rewrite()
• Same change PostgreSQL 9.5.6 · Fix performance problems in ts_rewrite()
• Same change PostgreSQL 9.3.16 · Fix performance problems in ts_rewrite()
• Same change PostgreSQL 9.2.20 · Fix performance problems in ts_rewrite()

“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.6.2 · Fix ts_rewrite()'s handling of nested NOT operators
• Same change PostgreSQL 9.5.6 · Fix ts_rewrite()'s handling of nested NOT operators
• Same change PostgreSQL 9.3.16 · Fix ts_rewrite()'s handling of nested NOT operators
• Same change PostgreSQL 9.2.20 · Fix ts_rewrite()'s handling of nested NOT 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 9.6.2 · Fix array_fill() to handle empty arrays properly
• Same change PostgreSQL 9.5.6 · Fix array_fill() to handle empty arrays properly
• Same change PostgreSQL 9.3.16 · Fix array_fill() to handle empty arrays properly
• Same change PostgreSQL 9.2.20 · Fix array_fill() to handle empty arrays properly

“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.6.2 · Fix one-byte buffer overrun in quote_literal_cstr()
• Same change PostgreSQL 9.5.6 · Fix one-byte buffer overrun in quote_literal_cstr()
• Same change PostgreSQL 9.3.16 · Fix one-byte buffer overrun in quote_literal_cstr()
• Same change PostgreSQL 9.2.20 · Fix one-byte buffer overrun in quote_literal_cstr()

“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.6.2 · Prevent multiple calls of pg_start_backup() and pg_stop_backup() from running concurrently
• Same change PostgreSQL 9.5.6 · Prevent multiple calls of pg_start_backup() and pg_stop_backup() from running concurrently
• Same change PostgreSQL 9.3.16 · Prevent multiple calls of pg_start_backup() and pg_stop_backup() from running concurrently
• Same change PostgreSQL 9.2.20 · Prevent multiple calls of pg_start_backup() and pg_stop_backup() from running concurrently

“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.6.2 · Avoid discarding interval-to-interval casts that aren't really no-ops
• Same change PostgreSQL 9.5.6 · Avoid discarding interval-to-interval casts that aren't really no-ops
• Same change PostgreSQL 9.3.16 · Avoid discarding interval-to-interval casts that aren't really no-ops
• Same change PostgreSQL 9.2.20 · Avoid discarding interval-to-interval casts that aren't really no-ops

“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.6.2 · Ensure that cached plans are invalidated by changes in foreign-table options
• Same change PostgreSQL 9.5.6 · Ensure that cached plans are invalidated by changes in foreign-table options
• Same change PostgreSQL 9.3.16 · Ensure that cached plans are invalidated by changes in foreign-table options

“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.6.2 · Fix pg_dump to dump user-defined casts and transforms that use built-in functions
• Same change PostgreSQL 9.5.6 · Fix pg_dump to dump user-defined casts and transforms that use built-in functions
• Same change PostgreSQL 9.3.16 · Fix pg_dump to dump user-defined casts and transforms that use built-in functions
• Same change PostgreSQL 9.2.20 · Fix pg_dump to dump user-defined casts and transforms that use built-in functions

“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.6.2 · Fix pg_restore with --create --if-exists to behave more sanely if an archive contains unrecognized DROP commands
• Same change PostgreSQL 9.5.6 · Fix pg_restore with --create --if-exists to behave more sanely if an archive contains unrecognized DROP commands

“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.6.2 · Fix pg_basebackup's rate limiting in the presence of slow I/O
• Same change PostgreSQL 9.5.6 · Fix pg_basebackup's rate limiting in the presence of slow I/O

“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.6.2 · Fix pg_basebackup's handling of symlinked pg_stat_tmp and pg_replslot subdirectories
• Same change PostgreSQL 9.5.6 · Fix pg_basebackup's handling of symlinked pg_stat_tmp and pg_replslot subdirectories

“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.6.2 · Fix possible pg_basebackup failure on standby server when including WAL files
• Same change PostgreSQL 9.5.6 · Fix possible pg_basebackup failure on standby server when including WAL files
• Same change PostgreSQL 9.3.16 · Fix possible pg_basebackup failure on standby server when including WAL files
• Same change PostgreSQL 9.2.20 · Fix possible pg_basebackup failure on standby server when including WAL 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 9.6.2 · Ensure that the Python exception objects we create for PL/Python are properly reference-counted
• Same change PostgreSQL 9.5.6 · Ensure that the Python exception objects we create for PL/Python are properly reference-counted
• Same change PostgreSQL 9.3.16 · Ensure that the Python exception objects we create for PL/Python are properly reference-counted
• Same change PostgreSQL 9.2.20 · Ensure that the Python exception objects we create for PL/Python are properly reference-counted

“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.6.2 · Fix PL/Tcl to support triggers on tables that have .tupno as a column name
• Same change PostgreSQL 9.5.6 · Fix PL/Tcl to support triggers on tables that have .tupno as a column name
• Same change PostgreSQL 9.3.16 · Fix PL/Tcl to support triggers on tables that have .tupno as a column name
• Same change PostgreSQL 9.2.20 · Fix PL/Tcl to support triggers on tables that have .tupno as a column name

“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.6.2 · Allow DOS-style line endings in ~/.pgpass files, even on Unix
• Same change PostgreSQL 9.5.6 · Allow DOS-style line endings in ~/.pgpass files, even on Unix
• Same change PostgreSQL 9.3.16 · Allow DOS-style line endings in ~/.pgpass files, even on Unix
• Same change PostgreSQL 9.2.20 · Allow DOS-style line endings in ~/.pgpass files, even on Unix

“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.6.2 · Fix one-byte buffer overrun if ecpg is given a file name that ends with a dot
• Same change PostgreSQL 9.5.6 · Fix one-byte buffer overrun if ecpg is given a file name that ends with a dot
• Same change PostgreSQL 9.3.16 · Fix one-byte buffer overrun if ecpg is given a file name that ends with a dot
• Same change PostgreSQL 9.2.20 · Fix one-byte buffer overrun if ecpg is given a file name that ends with a dot

“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.6.2 · Fix psql's tab completion for ALTER DEFAULT PRIVILEGES
• Same change PostgreSQL 9.5.6 · Fix psql's tab completion for ALTER DEFAULT PRIVILEGES
• Same change PostgreSQL 9.3.16 · Fix psql's tab completion for ALTER DEFAULT PRIVILEGES
• Same change PostgreSQL 9.2.20 · Fix psql's tab completion for ALTER DEFAULT PRIVILEGES

“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.6.2 · In psql, treat an empty or all-blank setting of the PAGER environment variable as meaning "no pager"
• Same change PostgreSQL 9.5.6 · In psql, treat an empty or all-blank setting of the PAGER environment variable as meaning "no pager"
• Same change PostgreSQL 9.3.16 · In psql, treat an empty or all-blank setting of the PAGER environment variable as meaning "no pager"
• Same change PostgreSQL 9.2.20 · In psql, treat an empty or all-blank setting of the PAGER environment variable as meaning "no pager"

“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.6.2 · Improve contrib/dblink's reporting of low-level libpq errors, such as out-of-memory
• Same change PostgreSQL 9.5.6 · Improve contrib/dblink's reporting of low-level libpq errors, such as out-of-memory
• Same change PostgreSQL 9.3.16 · Improve contrib/dblink's reporting of low-level libpq errors, such as out-of-memory
• Same change PostgreSQL 9.2.20 · Improve contrib/dblink's reporting of low-level libpq errors, such as out-of-memory

“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.6.2 · Teach contrib/dblink to ignore irrelevant server options when it uses a contrib/postgres_fdw foreign server as the source of connection options
• Same change PostgreSQL 9.5.6 · Teach contrib/dblink to ignore irrelevant server options when it uses a contrib/postgres_fdw foreign server as the source of connection options
• Same change PostgreSQL 9.3.16 · Teach contrib/dblink to ignore irrelevant server options when it uses a contrib/postgres_fdw foreign server as the source of connection options

“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.6.2 · On Windows, ensure that environment variable changes are propagated to DLLs built with debug options
• Same change PostgreSQL 9.5.6 · On Windows, ensure that environment variable changes are propagated to DLLs built with debug options
• Same change PostgreSQL 9.3.16 · On Windows, ensure that environment variable changes are propagated to DLLs built with debug options
• Same change PostgreSQL 9.2.20 · On Windows, ensure that environment variable changes are propagated to DLLs built with debug options

“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.6.2 · Sync our copy of the timezone library with IANA release tzcode2016j
• Same change PostgreSQL 9.5.6 · Sync our copy of the timezone library with IANA release tzcode2016j
• Same change PostgreSQL 9.3.16 · Sync our copy of the timezone library with IANA release tzcode2016j
• Same change PostgreSQL 9.2.20 · Sync our copy of the timezone library with IANA release tzcode2016j

“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.6.2 · Update time zone data files to tzdata release 2016j for DST law changes in northern Cyprus (adding a new zone Asia/Famagusta), Russia (adding a new zone Europe/Saratov), Tonga, and Antarctica/Casey. Historical corrections for Italy, Kazakhstan, Malta, and Palestine. Switch to preferring numeric zone abbreviations for Tonga.
• Same change PostgreSQL 9.5.6 · Update time zone data files to tzdata release 2016j for DST law changes in northern Cyprus (adding a new zone Asia/Famagusta), Russia (adding a new zone Europe/Saratov), Tonga, and Antarctica/Casey. Historical corrections for Italy, Kazakhstan, Malta, and Palestine. Switch to preferring numeric zone abbreviations for Tonga.
• Same change PostgreSQL 9.3.16 · Update time zone data files to tzdata release 2016j for DST law changes in northern Cyprus (adding a new zone Asia/Famagusta), Russia (adding a new zone Europe/Saratov), Tonga, and Antarctica/Casey. Historical corrections for Italy, Kazakhstan, Malta, and Palestine. Switch to preferring numeric zone abbreviations for Tonga.
• Same change PostgreSQL 9.2.20 · Update time zone data files to tzdata release 2016j for DST law changes in northern Cyprus (adding a new zone Asia/Famagusta), Russia (adding a new zone Europe/Saratov), Tonga, and Antarctica/Casey. Historical corrections for Italy, Kazakhstan, Malta, and Palestine. Switch to preferring numeric zone abbreviations for Tonga.

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