PostgreSQL 9.6.12 release changes

• Same change PostgreSQL 11.2 · By default, panic instead of retrying after fsync() failure, to avoid possible data corruption
• Same change PostgreSQL 10.7 · By default, panic instead of retrying after fsync() failure, to avoid possible data corruption
• Same change PostgreSQL 9.5.16 · By default, panic instead of retrying after fsync() failure, to avoid possible data corruption
• Same change PostgreSQL 9.4.21 · By default, panic instead of retrying after fsync() failure, to avoid possible data corruption

“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 11.2 · Include each major release branch's release notes in the documentation for only that branch, rather than that branch and all later ones
• Same change PostgreSQL 10.7 · Include each major release branch's release notes in the documentation for only that branch, rather than that branch and all later ones
• Same change PostgreSQL 9.5.16 · Include each major release branch's release notes in the documentation for only that branch, rather than that branch and all later ones
• Same change PostgreSQL 9.4.21 · Include each major release branch's release notes in the documentation for only that branch, rather than that branch and all later ones

“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 11.2 · Avoid possible deadlock when acquiring multiple buffer locks
• Same change PostgreSQL 10.7 · Avoid possible deadlock when acquiring multiple buffer locks
• Same change PostgreSQL 9.5.16 · Avoid possible deadlock when acquiring multiple buffer locks
• Same change PostgreSQL 9.4.21 · Avoid possible deadlock when acquiring multiple buffer locks

“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 11.2 · Avoid deadlock between hot-standby queries and replay of GIN index page deletion
• Same change PostgreSQL 10.7 · Avoid deadlock between hot-standby queries and replay of GIN index page deletion
• Same change PostgreSQL 9.5.16 · Avoid deadlock between hot-standby queries and replay of GIN index page deletion
• Same change PostgreSQL 9.4.21 · Avoid deadlock between hot-standby queries and replay of GIN index page deletion

“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 11.2 · Fix possible crashes in logical replication when index expressions or predicates are in use
• Same change PostgreSQL 10.7 · Fix possible crashes in logical replication when index expressions or predicates are in use
• Same change PostgreSQL 9.5.16 · Fix possible crashes in logical replication when index expressions or predicates are in use
• Same change PostgreSQL 9.4.21 · Fix possible crashes in logical replication when index expressions or predicates are in use

“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 11.2 · Avoid useless and expensive logical decoding of TOAST data during a table rewrite
• Same change PostgreSQL 10.7 · Avoid useless and expensive logical decoding of TOAST data during a table rewrite
• Same change PostgreSQL 9.5.16 · Avoid useless and expensive logical decoding of TOAST data during a table rewrite
• Same change PostgreSQL 9.4.21 · Avoid useless and expensive logical decoding of TOAST data during a table 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 11.2 · Fix logic for stopping a subset of WAL senders when synchronous replication is enabled
• Same change PostgreSQL 10.7 · Fix logic for stopping a subset of WAL senders when synchronous replication is enabled
• Same change PostgreSQL 9.5.16 · Fix logic for stopping a subset of WAL senders when synchronous replication is enabled
• Same change PostgreSQL 9.4.21 · Fix logic for stopping a subset of WAL senders when synchronous replication is enabled

“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 11.2 · Avoid possibly writing an incorrect replica identity field in a tuple deletion WAL record
• Same change PostgreSQL 10.7 · Avoid possibly writing an incorrect replica identity field in a tuple deletion WAL record
• Same change PostgreSQL 9.5.16 · Avoid possibly writing an incorrect replica identity field in a tuple deletion WAL record
• Same change PostgreSQL 9.4.21 · Avoid possibly writing an incorrect replica identity field in a tuple deletion WAL record

“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 11.2 · Make the archiver prioritize WAL history files over WAL data files while choosing which file to archive next
• Same change PostgreSQL 10.7 · Make the archiver prioritize WAL history files over WAL data files while choosing which file to archive next
• Same change PostgreSQL 9.5.16 · Make the archiver prioritize WAL history files over WAL data files while choosing which file to archive next

“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 11.2 · Fix possible crash in UPDATE with a multiple SET clause using a sub-SELECT as source
• Same change PostgreSQL 10.7 · Fix possible crash in UPDATE with a multiple SET clause using a sub-SELECT as source
• Same change PostgreSQL 9.5.16 · Fix possible crash in UPDATE with a multiple SET clause using a sub-SELECT as source

“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 11.2 · Avoid crash if libxml2 returns a null error message
• Same change PostgreSQL 10.7 · Avoid crash if libxml2 returns a null error message
• Same change PostgreSQL 9.5.16 · Avoid crash if libxml2 returns a null error message
• Same change PostgreSQL 9.4.21 · Avoid crash if libxml2 returns a null 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 11.2 · Fix spurious grouping-related parser errors caused by inconsistent handling of collation assignment
• Same change PostgreSQL 10.7 · Fix spurious grouping-related parser errors caused by inconsistent handling of collation assignment
• Same change PostgreSQL 9.5.16 · Fix spurious grouping-related parser errors caused by inconsistent handling of collation assignment
• Same change PostgreSQL 9.4.21 · Fix spurious grouping-related parser errors caused by inconsistent handling of collation assignment

“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 11.2 · Check whether the comparison function underlying LEAST() or GREATEST() is leakproof, rather than just assuming it is
• Same change PostgreSQL 10.7 · Check whether the comparison function underlying LEAST() or GREATEST() is leakproof, rather than just assuming it is
• Same change PostgreSQL 9.5.16 · Check whether the comparison function underlying LEAST() or GREATEST() is leakproof, rather than just assuming it is
• Same change PostgreSQL 9.4.21 · Check whether the comparison function underlying LEAST() or GREATEST() is leakproof, rather than just assuming it is

“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 11.2 · Fix incorrect planning of queries involving nested loops both above and below a Gather plan node
• Same change PostgreSQL 10.7 · Fix incorrect planning of queries involving nested loops both above and below a Gather plan node

“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 11.2 · Fix incorrect planning of queries in which a lateral reference must be evaluated at a foreign table scan
• Same change PostgreSQL 10.7 · Fix incorrect planning of queries in which a lateral reference must be evaluated at a foreign table scan
• Same change PostgreSQL 9.5.16 · Fix incorrect planning of queries in which a lateral reference must be evaluated at a foreign table scan
• Same change PostgreSQL 9.4.21 · Fix incorrect planning of queries in which a lateral reference must be evaluated at a foreign table scan

“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 11.2 · Fix corner-case underestimation of the cost of a merge join
• Same change PostgreSQL 10.7 · Fix corner-case underestimation of the cost of a merge join
• Same change PostgreSQL 9.5.16 · Fix corner-case underestimation of the cost of a merge join
• Same change PostgreSQL 9.4.21 · Fix corner-case underestimation of the cost of a merge join

“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 11.2 · Avoid O(N^2) planning time growth when a query contains many thousand indexable clauses
• Same change PostgreSQL 10.7 · Avoid O(N^2) planning time growth when a query contains many thousand indexable clauses
• Same change PostgreSQL 9.5.16 · Avoid O(N^2) planning time growth when a query contains many thousand indexable clauses
• Same change PostgreSQL 9.4.21 · Avoid O(N^2) planning time growth when a query contains many thousand indexable clauses

“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 11.2 · Improve ANALYZE's handling of concurrently-updated rows
• Same change PostgreSQL 10.7 · Improve ANALYZE's handling of concurrently-updated rows
• Same change PostgreSQL 9.5.16 · Improve ANALYZE's handling of concurrently-updated rows
• Same change PostgreSQL 9.4.21 · Improve ANALYZE's handling of concurrently-updated 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 11.2 · Make TRUNCATE ignore inheritance child tables that are temporary tables of other sessions
• Same change PostgreSQL 10.7 · Make TRUNCATE ignore inheritance child tables that are temporary tables of other sessions
• Same change PostgreSQL 9.5.16 · Make TRUNCATE ignore inheritance child tables that are temporary tables of other sessions
• Same change PostgreSQL 9.4.21 · Make TRUNCATE ignore inheritance child tables that are temporary tables of other sessions

“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 11.2 · Fix TRUNCATE to update the statistics counters for the right table
• Same change PostgreSQL 10.7 · Fix TRUNCATE to update the statistics counters for the right table
• Same change PostgreSQL 9.5.16 · Fix TRUNCATE to update the statistics counters for the right 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 11.2 · Process ALTER TABLE ONLY ADD COLUMN IF NOT EXISTS correctly
• Same change PostgreSQL 10.7 · Process ALTER TABLE ONLY ADD COLUMN IF NOT EXISTS correctly

“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 11.2 · Allow UNLISTEN in hot-standby mode
• Same change PostgreSQL 10.7 · Allow UNLISTEN in hot-standby mode
• Same change PostgreSQL 9.5.16 · Allow UNLISTEN in hot-standby mode
• Same change PostgreSQL 9.4.21 · Allow UNLISTEN in hot-standby 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 11.2 · Fix missing role dependencies in some schema and data type permissions lists
• Same change PostgreSQL 10.7 · Fix missing role dependencies in some schema and data type permissions lists
• Same change PostgreSQL 9.5.16 · Fix missing role dependencies in some schema and data type permissions lists
• Same change PostgreSQL 9.4.21 · Fix missing role dependencies in some schema and data type permissions lists

“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 11.2 · Ensure relation caches are updated properly after adding or removing foreign key constraints
• Same change PostgreSQL 10.7 · Ensure relation caches are updated properly after adding or removing foreign key constraints

“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 11.2 · Ensure relation caches are updated properly after renaming constraints
• Same change PostgreSQL 10.7 · Ensure relation caches are updated properly after renaming constraints
• Same change PostgreSQL 9.5.16 · Ensure relation caches are updated properly after renaming constraints
• Same change PostgreSQL 9.4.21 · Ensure relation caches are updated properly after renaming constraints

“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 10.7 · Make autovacuum more aggressive about removing leftover temporary tables, and also remove leftover temporary tables during DISCARD TEMP
• Same change PostgreSQL 9.5.16 · Make autovacuum more aggressive about removing leftover temporary tables, and also remove leftover temporary tables during DISCARD TEMP
• Same change PostgreSQL 9.4.21 · Make autovacuum more aggressive about removing leftover temporary tables, and also remove leftover temporary tables during DISCARD TEMP

“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 11.2 · Fix replay of GiST index micro-vacuum operations so that concurrent hot-standby queries do not see inconsistent state
• Same change PostgreSQL 10.7 · Fix replay of GiST index micro-vacuum operations so that concurrent hot-standby queries do not see inconsistent state

“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 11.2 · Prevent empty GIN index pages from being reclaimed too quickly, causing failures of concurrent searches
• Same change PostgreSQL 10.7 · Prevent empty GIN index pages from being reclaimed too quickly, causing failures of concurrent searches
• Same change PostgreSQL 9.5.16 · Prevent empty GIN index pages from being reclaimed too quickly, causing failures of concurrent searches
• Same change PostgreSQL 9.4.21 · Prevent empty GIN index pages from being reclaimed too quickly, causing failures of concurrent searches

“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 11.2 · Fix edge-case failures in float-to-integer coercions
• Same change PostgreSQL 10.7 · Fix edge-case failures in float-to-integer coercions
• Same change PostgreSQL 9.5.16 · Fix edge-case failures in float-to-integer coercions
• Same change PostgreSQL 9.4.21 · Fix edge-case failures in float-to-integer coercions

“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 11.2 · When making a PAM authentication request, don't set the PAM_RHOST variable if the connection is via a Unix socket
• Same change PostgreSQL 10.7 · When making a PAM authentication request, don't set the PAM_RHOST variable if the connection is via a Unix socket

“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 11.2 · Disallow setting client_min_messages higher than ERROR
• Same change PostgreSQL 10.7 · Disallow setting client_min_messages higher than ERROR
• Same change PostgreSQL 9.5.16 · Disallow setting client_min_messages higher than ERROR
• Same change PostgreSQL 9.4.21 · Disallow setting client_min_messages higher than ERROR

“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 11.2 · Fix ecpglib to use uselocale() or _configthreadlocale() in preference to setlocale()
• Same change PostgreSQL 10.7 · Fix ecpglib to use uselocale() or _configthreadlocale() in preference to setlocale()
• Same change PostgreSQL 9.5.16 · Fix ecpglib to use uselocale() or _configthreadlocale() in preference to setlocale()
• Same change PostgreSQL 9.4.21 · Fix ecpglib to use uselocale() or _configthreadlocale() in preference to setlocale()

“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 11.2 · Fix incorrect results for numeric data passed through an ecpg SQLDA (SQL Descriptor Area)
• Same change PostgreSQL 10.7 · Fix incorrect results for numeric data passed through an ecpg SQLDA (SQL Descriptor Area)
• Same change PostgreSQL 9.5.16 · Fix incorrect results for numeric data passed through an ecpg SQLDA (SQL Descriptor Area)
• Same change PostgreSQL 9.4.21 · Fix incorrect results for numeric data passed through an ecpg SQLDA (SQL Descriptor Area)

“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 11.2 · Fix psql's \g target meta-command to work with COPY TO STDOUT
• Same change PostgreSQL 10.7 · Fix psql's \g target meta-command to work with COPY TO STDOUT
• Same change PostgreSQL 9.5.16 · Fix psql's \g target meta-command to work with COPY TO STDOUT

“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 11.2 · Make psql's LaTeX output formats render special characters properly
• Same change PostgreSQL 10.7 · Make psql's LaTeX output formats render special characters properly
• Same change PostgreSQL 9.5.16 · Make psql's LaTeX output formats render special characters properly
• Same change PostgreSQL 9.4.21 · Make psql's LaTeX output formats render special characters 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 11.2 · Fix pg_dump's handling of materialized views with indirect dependencies on primary keys
• Same change PostgreSQL 10.7 · Fix pg_dump's handling of materialized views with indirect dependencies on primary keys
• Same change PostgreSQL 9.5.16 · Fix pg_dump's handling of materialized views with indirect dependencies on primary keys
• Same change PostgreSQL 9.4.21 · Fix pg_dump's handling of materialized views with indirect dependencies on primary keys

“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 11.2 · Avoid null-pointer-dereference crash on some platforms when pg_dump or pg_restore tries to report an error
• Same change PostgreSQL 10.7 · Avoid null-pointer-dereference crash on some platforms when pg_dump or pg_restore tries to report an error
• Same change PostgreSQL 9.5.16 · Avoid null-pointer-dereference crash on some platforms when pg_dump or pg_restore tries to report an error
• Same change PostgreSQL 9.4.21 · Avoid null-pointer-dereference crash on some platforms when pg_dump or pg_restore tries to report an error

“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 11.2 · Fix contrib/hstore to calculate correct hash values for empty hstore values that were created in version 8.4 or before
• Same change PostgreSQL 10.7 · Fix contrib/hstore to calculate correct hash values for empty hstore values that were created in version 8.4 or before
• Same change PostgreSQL 9.5.16 · Fix contrib/hstore to calculate correct hash values for empty hstore values that were created in version 8.4 or before
• Same change PostgreSQL 9.4.21 · Fix contrib/hstore to calculate correct hash values for empty hstore values that were created in version 8.4 or before

“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 11.2 · Avoid crashes and excessive runtime with large inputs to contrib/intarray's gist__int_ops index support
• Same change PostgreSQL 10.7 · Avoid crashes and excessive runtime with large inputs to contrib/intarray's gist__int_ops index support
• Same change PostgreSQL 9.5.16 · Avoid crashes and excessive runtime with large inputs to contrib/intarray's gist__int_ops index support
• Same change PostgreSQL 9.4.21 · Avoid crashes and excessive runtime with large inputs to contrib/intarray's gist__int_ops index support

“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 11.2 · Support new Makefile variables PG_CFLAGS, PG_CXXFLAGS, and PG_LDFLAGS in pgxs builds
• Same change PostgreSQL 10.7 · Support new Makefile variables PG_CFLAGS, PG_CXXFLAGS, and PG_LDFLAGS in pgxs builds
• Same change PostgreSQL 9.5.16 · Support new Makefile variables PG_CFLAGS, PG_CXXFLAGS, and PG_LDFLAGS in pgxs builds
• Same change PostgreSQL 9.4.21 · Support new Makefile variables PG_CFLAGS, PG_CXXFLAGS, and PG_LDFLAGS in pgxs builds

“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 11.2 · Fix Perl-coded build scripts to not assume “.” is in the search path, since recent Perl versions don't include that
• Same change PostgreSQL 10.7 · Fix Perl-coded build scripts to not assume “.” is in the search path, since recent Perl versions don't include that
• Same change PostgreSQL 9.5.16 · Fix Perl-coded build scripts to not assume "." is in the search path, since recent Perl versions don't include that
• Same change PostgreSQL 9.4.21 · Fix Perl-coded build scripts to not assume "." is in the search path, since recent Perl versions don't include that

“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 11.2 · Fix server command-line option parsing problems on OpenBSD
• Same change PostgreSQL 10.7 · Fix server command-line option parsing problems on OpenBSD
• Same change PostgreSQL 9.5.16 · Fix server command-line option parsing problems on OpenBSD
• Same change PostgreSQL 9.4.21 · Fix server command-line option parsing problems on OpenBSD

“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 11.2 · Relocate call of set_rel_pathlist_hook so that extensions can use it to supply partial paths for parallel queries
• Same change PostgreSQL 10.7 · Relocate call of set_rel_pathlist_hook so that extensions can use it to supply partial paths for parallel 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 11.2 · Update time zone data files to tzdata release 2018i for DST law changes in Kazakhstan, Metlakatla, and Sao Tome and Principe. Kazakhstan's Qyzylorda zone is split in two, creating a new zone Asia/Qostanay, as some areas did not change UTC offset. Historical corrections for Hong Kong and numerous Pacific islands.
• Same change PostgreSQL 10.7 · Update time zone data files to tzdata release 2018i for DST law changes in Kazakhstan, Metlakatla, and Sao Tome and Principe. Kazakhstan's Qyzylorda zone is split in two, creating a new zone Asia/Qostanay, as some areas did not change UTC offset. Historical corrections for Hong Kong and numerous Pacific islands.
• Same change PostgreSQL 9.5.16 · Update time zone data files to tzdata release 2018i for DST law changes in Kazakhstan, Metlakatla, and Sao Tome and Principe. Kazakhstan's Qyzylorda zone is split in two, creating a new zone Asia/Qostanay, as some areas did not change UTC offset. Historical corrections for Hong Kong and numerous Pacific islands.
• Same change PostgreSQL 9.4.21 · Update time zone data files to tzdata release 2018i for DST law changes in Kazakhstan, Metlakatla, and Sao Tome and Principe. Kazakhstan's Qyzylorda zone is split in two, creating a new zone Asia/Qostanay, as some areas did not change UTC offset. Historical corrections for Hong Kong and numerous Pacific islands.

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