From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Sun, 25 Feb 2018 19:52:51 +0000 (-0500)
Subject: Release notes for 10.3, 9.6.8, 9.5.12, 9.4.17, 9.3.22.
X-Git-Tag: REL_11_BETA1~719
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=1316417bbab0821f99eb21c0b654e33f5f6f90a4;p=postgresql
Release notes for 10.3, 9.6.8, 9.5.12, 9.4.17, 9.3.22.
---
diff --git a/doc/src/sgml/release-10.sgml b/doc/src/sgml/release-10.sgml
index 718ad4cb0c..d543849715 100644
--- a/doc/src/sgml/release-10.sgml
+++ b/doc/src/sgml/release-10.sgml
@@ -35,6 +35,27 @@
<listitem>
<!--
+Author: Peter Eisentraut <peter_e@gmx.net>
+Branch: master [bc1adc651] 2018-02-23 22:13:21 -0500
+Branch: REL_10_STABLE [b9bf23abb] 2018-02-23 22:09:26 -0500
+-->
+ <para>
+ Prevent logical replication from trying to ship changes for
+ unpublishable relations (Peter Eisentraut)
+ </para>
+
+ <para>
+ A publication marked <literal>FOR ALL TABLES</literal> would
+ incorrectly ship changes in materialized views
+ and <structname>information_schema</structname> tables, which are
+ supposed to be omitted from the change stream.
+ </para>
+ <para>
+ </para>
+ </listitem>
+
+ <listitem>
+<!--
Author: Tom Lane <tgl@sss.pgh.pa.us>
Branch: master [159efe4af] 2018-02-19 16:00:31 -0500
Branch: REL_10_STABLE [517e0fe86] 2018-02-19 16:00:18 -0500
diff --git a/doc/src/sgml/release-9.3.sgml b/doc/src/sgml/release-9.3.sgml
index 31972e5a6f..f059bbbbc3 100644
--- a/doc/src/sgml/release-9.3.sgml
+++ b/doc/src/sgml/release-9.3.sgml
@@ -1,6 +1,118 @@
<!-- doc/src/sgml/release-9.3.sgml -->
<!-- See header comment in release.sgml about typical markup -->
+ <sect1 id="release-9-3-22">
+ <title>Release 9.3.22</title>
+
+ <formalpara>
+ <title>Release date:</title>
+ <para>2018-03-01</para>
+ </formalpara>
+
+ <para>
+ This release contains a variety of fixes from 9.3.21.
+ For information about new features in the 9.3 major release, see
+ <xref linkend="release-9-3"/>.
+ </para>
+
+ <sect2>
+ <title>Migration to Version 9.3.22</title>
+
+ <para>
+ A dump/restore is not required for those running 9.3.X.
+ </para>
+
+ <para>
+ However, if you are upgrading from a version earlier than 9.3.18,
+ see <xref linkend="release-9-3-18"/>.
+ </para>
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Fix misbehavior of concurrent-update rechecks with CTE references
+ appearing in subplans (Tom Lane)
+ </para>
+
+ <para>
+ If a CTE (<literal>WITH</literal> 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.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix planner failures with overlapping mergejoin clauses in an outer
+ join (Tom Lane)
+ </para>
+
+ <para>
+ These mistakes led to <quote>left and right pathkeys do not match in
+ mergejoin</quote> or <quote>outer pathkeys do not match
+ mergeclauses</quote> planner errors in corner cases.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Repair <application>pg_upgrade</application>'s failure to
+ preserve <structfield>relfrozenxid</structfield> for materialized
+ views (Tom Lane, Andres Freund)
+ </para>
+
+ <para>
+ This oversight could lead to data corruption in materialized views
+ after an upgrade, manifesting as <quote>could not access status of
+ transaction</quote> or <quote>found xmin from before
+ relfrozenxid</quote> errors. The problem would be more likely to
+ occur in seldom-refreshed materialized views, or ones that were
+ maintained only with <command>REFRESH MATERIALIZED VIEW
+ CONCURRENTLY</command>.
+ </para>
+
+ <para>
+ If such corruption is observed, it can be repaired by refreshing the
+ materialized view (without <literal>CONCURRENTLY</literal>).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix incorrect reporting of PL/Python function names in
+ error <literal>CONTEXT</literal> stacks (Tom Lane)
+ </para>
+
+ <para>
+ 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 <literal>DO</literal> block could result in a null pointer
+ dereference crash on some platforms.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Allow <filename>contrib/auto_explain</filename>'s
+ <varname>log_min_duration</varname> setting to range up
+ to <literal>INT_MAX</literal>, or about 24 days instead of 35 minutes
+ (Tom Lane)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-9-3-21">
<title>Release 9.3.21</title>
diff --git a/doc/src/sgml/release-9.4.sgml b/doc/src/sgml/release-9.4.sgml
index c524271e90..68ac961436 100644
--- a/doc/src/sgml/release-9.4.sgml
+++ b/doc/src/sgml/release-9.4.sgml
@@ -1,6 +1,118 @@
<!-- doc/src/sgml/release-9.4.sgml -->
<!-- See header comment in release.sgml about typical markup -->
+ <sect1 id="release-9-4-17">
+ <title>Release 9.4.17</title>
+
+ <formalpara>
+ <title>Release date:</title>
+ <para>2018-03-01</para>
+ </formalpara>
+
+ <para>
+ This release contains a variety of fixes from 9.4.16.
+ For information about new features in the 9.4 major release, see
+ <xref linkend="release-9-4"/>.
+ </para>
+
+ <sect2>
+ <title>Migration to Version 9.4.17</title>
+
+ <para>
+ A dump/restore is not required for those running 9.4.X.
+ </para>
+
+ <para>
+ However, if you are upgrading from a version earlier than 9.4.13,
+ see <xref linkend="release-9-4-13"/>.
+ </para>
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Fix misbehavior of concurrent-update rechecks with CTE references
+ appearing in subplans (Tom Lane)
+ </para>
+
+ <para>
+ If a CTE (<literal>WITH</literal> 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.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix planner failures with overlapping mergejoin clauses in an outer
+ join (Tom Lane)
+ </para>
+
+ <para>
+ These mistakes led to <quote>left and right pathkeys do not match in
+ mergejoin</quote> or <quote>outer pathkeys do not match
+ mergeclauses</quote> planner errors in corner cases.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Repair <application>pg_upgrade</application>'s failure to
+ preserve <structfield>relfrozenxid</structfield> for materialized
+ views (Tom Lane, Andres Freund)
+ </para>
+
+ <para>
+ This oversight could lead to data corruption in materialized views
+ after an upgrade, manifesting as <quote>could not access status of
+ transaction</quote> or <quote>found xmin from before
+ relfrozenxid</quote> errors. The problem would be more likely to
+ occur in seldom-refreshed materialized views, or ones that were
+ maintained only with <command>REFRESH MATERIALIZED VIEW
+ CONCURRENTLY</command>.
+ </para>
+
+ <para>
+ If such corruption is observed, it can be repaired by refreshing the
+ materialized view (without <literal>CONCURRENTLY</literal>).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix incorrect reporting of PL/Python function names in
+ error <literal>CONTEXT</literal> stacks (Tom Lane)
+ </para>
+
+ <para>
+ 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 <literal>DO</literal> block could result in a null pointer
+ dereference crash on some platforms.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Allow <filename>contrib/auto_explain</filename>'s
+ <varname>log_min_duration</varname> setting to range up
+ to <literal>INT_MAX</literal>, or about 24 days instead of 35 minutes
+ (Tom Lane)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-9-4-16">
<title>Release 9.4.16</title>
diff --git a/doc/src/sgml/release-9.5.sgml b/doc/src/sgml/release-9.5.sgml
index ab92fb0134..cb545b08ab 100644
--- a/doc/src/sgml/release-9.5.sgml
+++ b/doc/src/sgml/release-9.5.sgml
@@ -1,6 +1,118 @@
<!-- doc/src/sgml/release-9.5.sgml -->
<!-- See header comment in release.sgml about typical markup -->
+ <sect1 id="release-9-5-12">
+ <title>Release 9.5.12</title>
+
+ <formalpara>
+ <title>Release date:</title>
+ <para>2018-03-01</para>
+ </formalpara>
+
+ <para>
+ This release contains a variety of fixes from 9.5.11.
+ For information about new features in the 9.5 major release, see
+ <xref linkend="release-9-5"/>.
+ </para>
+
+ <sect2>
+ <title>Migration to Version 9.5.12</title>
+
+ <para>
+ A dump/restore is not required for those running 9.5.X.
+ </para>
+
+ <para>
+ However, if you are upgrading from a version earlier than 9.5.10,
+ see <xref linkend="release-9-5-10"/>.
+ </para>
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Fix misbehavior of concurrent-update rechecks with CTE references
+ appearing in subplans (Tom Lane)
+ </para>
+
+ <para>
+ If a CTE (<literal>WITH</literal> 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.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix planner failures with overlapping mergejoin clauses in an outer
+ join (Tom Lane)
+ </para>
+
+ <para>
+ These mistakes led to <quote>left and right pathkeys do not match in
+ mergejoin</quote> or <quote>outer pathkeys do not match
+ mergeclauses</quote> planner errors in corner cases.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Repair <application>pg_upgrade</application>'s failure to
+ preserve <structfield>relfrozenxid</structfield> for materialized
+ views (Tom Lane, Andres Freund)
+ </para>
+
+ <para>
+ This oversight could lead to data corruption in materialized views
+ after an upgrade, manifesting as <quote>could not access status of
+ transaction</quote> or <quote>found xmin from before
+ relfrozenxid</quote> errors. The problem would be more likely to
+ occur in seldom-refreshed materialized views, or ones that were
+ maintained only with <command>REFRESH MATERIALIZED VIEW
+ CONCURRENTLY</command>.
+ </para>
+
+ <para>
+ If such corruption is observed, it can be repaired by refreshing the
+ materialized view (without <literal>CONCURRENTLY</literal>).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix incorrect reporting of PL/Python function names in
+ error <literal>CONTEXT</literal> stacks (Tom Lane)
+ </para>
+
+ <para>
+ 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 <literal>DO</literal> block could result in a null pointer
+ dereference crash on some platforms.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Allow <filename>contrib/auto_explain</filename>'s
+ <varname>log_min_duration</varname> setting to range up
+ to <literal>INT_MAX</literal>, or about 24 days instead of 35 minutes
+ (Tom Lane)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-9-5-11">
<title>Release 9.5.11</title>
diff --git a/doc/src/sgml/release-9.6.sgml b/doc/src/sgml/release-9.6.sgml
index 6d7a500933..62d0594a00 100644
--- a/doc/src/sgml/release-9.6.sgml
+++ b/doc/src/sgml/release-9.6.sgml
@@ -1,6 +1,125 @@
<!-- doc/src/sgml/release-9.6.sgml -->
<!-- See header comment in release.sgml about typical markup -->
+ <sect1 id="release-9-6-8">
+ <title>Release 9.6.8</title>
+
+ <formalpara>
+ <title>Release date:</title>
+ <para>2018-03-01</para>
+ </formalpara>
+
+ <para>
+ This release contains a variety of fixes from 9.6.7.
+ For information about new features in the 9.6 major release, see
+ <xref linkend="release-9-6"/>.
+ </para>
+
+ <sect2>
+ <title>Migration to Version 9.6.8</title>
+
+ <para>
+ A dump/restore is not required for those running 9.6.X.
+ </para>
+
+ <para>
+ However, if you are upgrading from a version earlier than 9.6.7,
+ see <xref linkend="release-9-6-7"/>.
+ </para>
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Fix misbehavior of concurrent-update rechecks with CTE references
+ appearing in subplans (Tom Lane)
+ </para>
+
+ <para>
+ If a CTE (<literal>WITH</literal> 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.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix planner failures with overlapping mergejoin clauses in an outer
+ join (Tom Lane)
+ </para>
+
+ <para>
+ These mistakes led to <quote>left and right pathkeys do not match in
+ mergejoin</quote> or <quote>outer pathkeys do not match
+ mergeclauses</quote> planner errors in corner cases.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Repair <application>pg_upgrade</application>'s failure to
+ preserve <structfield>relfrozenxid</structfield> for materialized
+ views (Tom Lane, Andres Freund)
+ </para>
+
+ <para>
+ This oversight could lead to data corruption in materialized views
+ after an upgrade, manifesting as <quote>could not access status of
+ transaction</quote> or <quote>found xmin from before
+ relfrozenxid</quote> errors. The problem would be more likely to
+ occur in seldom-refreshed materialized views, or ones that were
+ maintained only with <command>REFRESH MATERIALIZED VIEW
+ CONCURRENTLY</command>.
+ </para>
+
+ <para>
+ If such corruption is observed, it can be repaired by refreshing the
+ materialized view (without <literal>CONCURRENTLY</literal>).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix incorrect reporting of PL/Python function names in
+ error <literal>CONTEXT</literal> stacks (Tom Lane)
+ </para>
+
+ <para>
+ 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 <literal>DO</literal> block could result in a null pointer
+ dereference crash on some platforms.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Allow <filename>contrib/auto_explain</filename>'s
+ <varname>log_min_duration</varname> setting to range up
+ to <literal>INT_MAX</literal>, or about 24 days instead of 35 minutes
+ (Tom Lane)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Mark assorted GUC variables as <literal>PGDLLIMPORT</literal>, to
+ ease porting extension modules to Windows (Metin Doslu)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-9-6-7">
<title>Release 9.6.7</title>