+ Prevent logical replication from trying to ship changes for
+ unpublishable relations (Peter Eisentraut)
+
+
+ A publication marked FOR ALL TABLES would
+ incorrectly ship changes in materialized views
+ and information_schema tables, which are
+ supposed to be omitted from the change stream.
+
+
+
+
+
+
+
+
Release 9.3.22
+
+
+
Release date:
+
+
+ This release contains a variety of fixes from 9.3.21.
+ For information about new features in the 9.3 major release, see
+ .
+
+
+
+
Migration to Version 9.3.22
+
+ A dump/restore is not required for those running 9.3.X.
+
+
+ However, if you are upgrading from a version earlier than 9.3.18,
+ see .
+
+
+
+
+
Changes
+
+
+
+
+ Fix misbehavior of concurrent-update rechecks with CTE references
+ appearing in subplans (Tom Lane)
+
+
+ If a CTE (WITH clause reference) is used in an
+ InitPlan or SubPlan, and the query requires a recheck due to trying
+ to update or lock a concurrently-updated row, incorrect results could
+ be obtained.
+
+
+
+
+ Fix planner failures with overlapping mergejoin clauses in an outer
+ join (Tom Lane)
+
+
+ These mistakes led to left and right pathkeys do not match in
+ mergejoin or outer pathkeys do not match
+ mergeclauses planner errors in corner cases.
+
+
+
+
+ Repair
pg_upgrade's failure to
+ preserve relfrozenxid for materialized
+ views (Tom Lane, Andres Freund)
+
+
+ This oversight could lead to data corruption in materialized views
+ after an upgrade, manifesting as could not access status of
+ transaction or found xmin from before
+ relfrozenxid errors. The problem would be more likely to
+ occur in seldom-refreshed materialized views, or ones that were
+ maintained only with REFRESH MATERIALIZED VIEW
+ CONCURRENTLY.
+
+
+ If such corruption is observed, it can be repaired by refreshing the
+ materialized view (without CONCURRENTLY).
+
+
+
+
+ Fix incorrect reporting of PL/Python function names in
+ error CONTEXT stacks (Tom Lane)
+
+
+ An error occurring within a nested PL/Python function call (that is,
+ one reached via a SPI query from another PL/Python function) would
+ result in a stack trace showing the inner function's name twice,
+ rather than the expected results. Also, an error in a nested
+ PL/Python DO block could result in a null pointer
+ dereference crash on some platforms.
+
+
+
+
+ Allow contrib/auto_explain's
+ log_min_duration setting to range up
+ to INT_MAX, or about 24 days instead of 35 minutes
+ (Tom Lane)
+
+
+
+
+
+
+
+
Release 9.3.21
+
+
Release 9.4.17
+
+
+
Release date:
+
+
+ This release contains a variety of fixes from 9.4.16.
+ For information about new features in the 9.4 major release, see
+ .
+
+
+
+
Migration to Version 9.4.17
+
+ A dump/restore is not required for those running 9.4.X.
+
+
+ However, if you are upgrading from a version earlier than 9.4.13,
+ see .
+
+
+
+
+
Changes
+
+
+
+
+ Fix misbehavior of concurrent-update rechecks with CTE references
+ appearing in subplans (Tom Lane)
+
+
+ If a CTE (WITH clause reference) is used in an
+ InitPlan or SubPlan, and the query requires a recheck due to trying
+ to update or lock a concurrently-updated row, incorrect results could
+ be obtained.
+
+
+
+
+ Fix planner failures with overlapping mergejoin clauses in an outer
+ join (Tom Lane)
+
+
+ These mistakes led to left and right pathkeys do not match in
+ mergejoin or outer pathkeys do not match
+ mergeclauses planner errors in corner cases.
+
+
+
+
+ Repair
pg_upgrade's failure to
+ preserve relfrozenxid for materialized
+ views (Tom Lane, Andres Freund)
+
+
+ This oversight could lead to data corruption in materialized views
+ after an upgrade, manifesting as could not access status of
+ transaction or found xmin from before
+ relfrozenxid errors. The problem would be more likely to
+ occur in seldom-refreshed materialized views, or ones that were
+ maintained only with REFRESH MATERIALIZED VIEW
+ CONCURRENTLY.
+
+
+ If such corruption is observed, it can be repaired by refreshing the
+ materialized view (without CONCURRENTLY).
+
+
+
+
+ Fix incorrect reporting of PL/Python function names in
+ error CONTEXT stacks (Tom Lane)
+
+
+ An error occurring within a nested PL/Python function call (that is,
+ one reached via a SPI query from another PL/Python function) would
+ result in a stack trace showing the inner function's name twice,
+ rather than the expected results. Also, an error in a nested
+ PL/Python DO block could result in a null pointer
+ dereference crash on some platforms.
+
+
+
+
+ Allow contrib/auto_explain's
+ log_min_duration setting to range up
+ to INT_MAX, or about 24 days instead of 35 minutes
+ (Tom Lane)
+
+
+
+
+
+
+
+
Release 9.4.16
+
+
Release 9.5.12
+
+
+
Release date:
+
+
+ This release contains a variety of fixes from 9.5.11.
+ For information about new features in the 9.5 major release, see
+ .
+
+
+
+
Migration to Version 9.5.12
+
+ A dump/restore is not required for those running 9.5.X.
+
+
+ However, if you are upgrading from a version earlier than 9.5.10,
+ see .
+
+
+
+
+
Changes
+
+
+
+
+ Fix misbehavior of concurrent-update rechecks with CTE references
+ appearing in subplans (Tom Lane)
+
+
+ If a CTE (WITH clause reference) is used in an
+ InitPlan or SubPlan, and the query requires a recheck due to trying
+ to update or lock a concurrently-updated row, incorrect results could
+ be obtained.
+
+
+
+
+ Fix planner failures with overlapping mergejoin clauses in an outer
+ join (Tom Lane)
+
+
+ These mistakes led to left and right pathkeys do not match in
+ mergejoin or outer pathkeys do not match
+ mergeclauses planner errors in corner cases.
+
+
+
+
+ Repair
pg_upgrade's failure to
+ preserve relfrozenxid for materialized
+ views (Tom Lane, Andres Freund)
+
+
+ This oversight could lead to data corruption in materialized views
+ after an upgrade, manifesting as could not access status of
+ transaction or found xmin from before
+ relfrozenxid errors. The problem would be more likely to
+ occur in seldom-refreshed materialized views, or ones that were
+ maintained only with REFRESH MATERIALIZED VIEW
+ CONCURRENTLY.
+
+
+ If such corruption is observed, it can be repaired by refreshing the
+ materialized view (without CONCURRENTLY).
+
+
+
+
+ Fix incorrect reporting of PL/Python function names in
+ error CONTEXT stacks (Tom Lane)
+
+
+ An error occurring within a nested PL/Python function call (that is,
+ one reached via a SPI query from another PL/Python function) would
+ result in a stack trace showing the inner function's name twice,
+ rather than the expected results. Also, an error in a nested
+ PL/Python DO block could result in a null pointer
+ dereference crash on some platforms.
+
+
+
+
+ Allow contrib/auto_explain's
+ log_min_duration setting to range up
+ to INT_MAX, or about 24 days instead of 35 minutes
+ (Tom Lane)
+
+
+
+
+
+
+
+
Release 9.5.11
+
+
Release 9.6.8
+
+
+
Release date:
+
+
+ This release contains a variety of fixes from 9.6.7.
+ For information about new features in the 9.6 major release, see
+ .
+
+
+
+
Migration to Version 9.6.8
+
+ A dump/restore is not required for those running 9.6.X.
+
+
+ However, if you are upgrading from a version earlier than 9.6.7,
+ see .
+
+
+
+
+
Changes
+
+
+
+
+ Fix misbehavior of concurrent-update rechecks with CTE references
+ appearing in subplans (Tom Lane)
+
+
+ If a CTE (WITH clause reference) is used in an
+ InitPlan or SubPlan, and the query requires a recheck due to trying
+ to update or lock a concurrently-updated row, incorrect results could
+ be obtained.
+
+
+
+
+ Fix planner failures with overlapping mergejoin clauses in an outer
+ join (Tom Lane)
+
+
+ These mistakes led to left and right pathkeys do not match in
+ mergejoin or outer pathkeys do not match
+ mergeclauses planner errors in corner cases.
+
+
+
+
+ Repair
pg_upgrade's failure to
+ preserve relfrozenxid for materialized
+ views (Tom Lane, Andres Freund)
+
+
+ This oversight could lead to data corruption in materialized views
+ after an upgrade, manifesting as could not access status of
+ transaction or found xmin from before
+ relfrozenxid errors. The problem would be more likely to
+ occur in seldom-refreshed materialized views, or ones that were
+ maintained only with REFRESH MATERIALIZED VIEW
+ CONCURRENTLY.
+
+
+ If such corruption is observed, it can be repaired by refreshing the
+ materialized view (without CONCURRENTLY).
+
+
+
+
+ Fix incorrect reporting of PL/Python function names in
+ error CONTEXT stacks (Tom Lane)
+
+
+ An error occurring within a nested PL/Python function call (that is,
+ one reached via a SPI query from another PL/Python function) would
+ result in a stack trace showing the inner function's name twice,
+ rather than the expected results. Also, an error in a nested
+ PL/Python DO block could result in a null pointer
+ dereference crash on some platforms.
+
+
+
+
+ Allow contrib/auto_explain's
+ log_min_duration setting to range up
+ to INT_MAX, or about 24 days instead of 35 minutes
+ (Tom Lane)
+
+
+
+
+ Mark assorted GUC variables as PGDLLIMPORT, to
+ ease porting extension modules to Windows (Metin Doslu)
+
+
+
+
+
+
+
+
Release 9.6.7
projects / postgresql.git / commitdiff