diff --git a/doc/src/sgml/release-9.0.sgml b/doc/src/sgml/release-9.0.sgml
index 9794b5b3b76ec4eaab0b8bdb3d5f7d8a7f397718..80cd1c43cdcc4c944d29a9eb9a1e064c9711c647 100644
--- a/doc/src/sgml/release-9.0.sgml
+++ b/doc/src/sgml/release-9.0.sgml
@@ -1,6 +1,100 @@
<!-- doc/src/sgml/release-9.0.sgml -->
<!-- See header comment in release.sgml about typical markup -->
+ <sect1 id="release-9-0-21">
+ <title>Release 9.0.21</title>
+
+ <note>
+ <title>Release Date</title>
+ <simpara>2015-06-04</simpara>
+ </note>
+
+ <para>
+ This release contains a small number of fixes from 9.0.20.
+ For information about new features in the 9.0 major release, see
+ <xref linkend="release-9-0">.
+ </para>
+
+ <para>
+ The <productname>PostgreSQL</> community will stop releasing updates
+ for the 9.0.X release series in September 2015.
+ Users are encouraged to update to a newer release branch soon.
+ </para>
+
+ <sect2>
+ <title>Migration to Version 9.0.21</title>
+
+ <para>
+ A dump/restore is not required for those running 9.0.X.
+ </para>
+
+ <para>
+ However, if you are upgrading from a version earlier than 9.0.18,
+ see <xref linkend="release-9-0-18">.
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Avoid failures while <function>fsync</>'ing data directory during
+ crash restart (Abhijit Menon-Sen, Tom Lane)
+ </para>
+
+ <para>
+ In the previous minor releases we added a patch to <function>fsync</>
+ everything in the data directory after a crash. Unfortunately its
+ response to any error condition was to fail, thereby preventing the
+ server from starting up, even when the problem was quite harmless.
+ An example is that an unwritable file in the data directory would
+ prevent restart on some platforms; but it is common to make SSL
+ certificate files unwritable by the server. Revise this behavior so
+ that permissions failures are ignored altogether, and other types of
+ failures are logged but do not prevent continuing.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Remove <application>configure</>'s check prohibiting linking to a
+ threaded <application>libpython</>
+ on <systemitem class="osname">OpenBSD</> (Tom Lane)
+ </para>
+
+ <para>
+ The failure this restriction was meant to prevent seems to not be a
+ problem anymore on current <systemitem class="osname">OpenBSD</>
+ versions.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Allow <application>libpq</> to use TLS protocol versions beyond v1
+ (Noah Misch)
+ </para>
+
+ <para>
+ For a long time, <application>libpq</> was coded so that the only SSL
+ protocol it would allow was TLS v1. Now that newer TLS versions are
+ becoming popular, allow it to negotiate the highest commonly-supported
+ TLS version with the server. (<productname>PostgreSQL</> servers were
+ already capable of such negotiation, so no change is needed on the
+ server side.) This is a back-patch of a change already released in
+ 9.4.0.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-9-0-20">
<title>Release 9.0.20</title>
@@ -169,6 +263,13 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ Avoid <quote>cannot GetMultiXactIdMembers() during recovery</> error
+ (Álvaro Herrera)
+ </para>
+ </listitem>
+
<listitem>
<para>
Recursively <function>fsync()</> the data directory after a crash
diff --git a/doc/src/sgml/release-9.1.sgml b/doc/src/sgml/release-9.1.sgml
index f6c0d1315769cd78b685544dd2876f87d62f2c00..8306cfab0394444ee02ceb5c535ba1bd7d013f54 100644
--- a/doc/src/sgml/release-9.1.sgml
+++ b/doc/src/sgml/release-9.1.sgml
@@ -1,6 +1,94 @@
<!-- doc/src/sgml/release-9.1.sgml -->
<!-- See header comment in release.sgml about typical markup -->
+ <sect1 id="release-9-1-17">
+ <title>Release 9.1.17</title>
+
+ <note>
+ <title>Release Date</title>
+ <simpara>2015-06-04</simpara>
+ </note>
+
+ <para>
+ This release contains a small number of fixes from 9.1.16.
+ For information about new features in the 9.1 major release, see
+ <xref linkend="release-9-1">.
+ </para>
+
+ <sect2>
+ <title>Migration to Version 9.1.17</title>
+
+ <para>
+ A dump/restore is not required for those running 9.1.X.
+ </para>
+
+ <para>
+ However, if you are upgrading from a version earlier than 9.1.16,
+ see <xref linkend="release-9-1-16">.
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Avoid failures while <function>fsync</>'ing data directory during
+ crash restart (Abhijit Menon-Sen, Tom Lane)
+ </para>
+
+ <para>
+ In the previous minor releases we added a patch to <function>fsync</>
+ everything in the data directory after a crash. Unfortunately its
+ response to any error condition was to fail, thereby preventing the
+ server from starting up, even when the problem was quite harmless.
+ An example is that an unwritable file in the data directory would
+ prevent restart on some platforms; but it is common to make SSL
+ certificate files unwritable by the server. Revise this behavior so
+ that permissions failures are ignored altogether, and other types of
+ failures are logged but do not prevent continuing.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Remove <application>configure</>'s check prohibiting linking to a
+ threaded <application>libpython</>
+ on <systemitem class="osname">OpenBSD</> (Tom Lane)
+ </para>
+
+ <para>
+ The failure this restriction was meant to prevent seems to not be a
+ problem anymore on current <systemitem class="osname">OpenBSD</>
+ versions.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Allow <application>libpq</> to use TLS protocol versions beyond v1
+ (Noah Misch)
+ </para>
+
+ <para>
+ For a long time, <application>libpq</> was coded so that the only SSL
+ protocol it would allow was TLS v1. Now that newer TLS versions are
+ becoming popular, allow it to negotiate the highest commonly-supported
+ TLS version with the server. (<productname>PostgreSQL</> servers were
+ already capable of such negotiation, so no change is needed on the
+ server side.) This is a back-patch of a change already released in
+ 9.4.0.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-9-1-16">
<title>Release 9.1.16</title>
@@ -201,6 +289,13 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ Avoid <quote>cannot GetMultiXactIdMembers() during recovery</> error
+ (Álvaro Herrera)
+ </para>
+ </listitem>
+
<listitem>
<para>
Recursively <function>fsync()</> the data directory after a crash
diff --git a/doc/src/sgml/release-9.2.sgml b/doc/src/sgml/release-9.2.sgml
index 168a387d345c0d37508a92877d9466b3abeb0e3f..ef4ce98e5385c4a553d923ffd623c7616f04487e 100644
--- a/doc/src/sgml/release-9.2.sgml
+++ b/doc/src/sgml/release-9.2.sgml
@@ -1,6 +1,101 @@
<!-- doc/src/sgml/release-9.2.sgml -->
<!-- See header comment in release.sgml about typical markup -->
+ <sect1 id="release-9-2-12">
+ <title>Release 9.2.12</title>
+
+ <note>
+ <title>Release Date</title>
+ <simpara>2015-06-04</simpara>
+ </note>
+
+ <para>
+ This release contains a small number of fixes from 9.2.11.
+ For information about new features in the 9.2 major release, see
+ <xref linkend="release-9-2">.
+ </para>
+
+ <sect2>
+ <title>Migration to Version 9.2.12</title>
+
+ <para>
+ A dump/restore is not required for those running 9.2.X.
+ </para>
+
+ <para>
+ However, if you are upgrading from a version earlier than 9.2.11,
+ see <xref linkend="release-9-2-11">.
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Avoid failures while <function>fsync</>'ing data directory during
+ crash restart (Abhijit Menon-Sen, Tom Lane)
+ </para>
+
+ <para>
+ In the previous minor releases we added a patch to <function>fsync</>
+ everything in the data directory after a crash. Unfortunately its
+ response to any error condition was to fail, thereby preventing the
+ server from starting up, even when the problem was quite harmless.
+ An example is that an unwritable file in the data directory would
+ prevent restart on some platforms; but it is common to make SSL
+ certificate files unwritable by the server. Revise this behavior so
+ that permissions failures are ignored altogether, and other types of
+ failures are logged but do not prevent continuing.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <function>pg_get_functiondef()</> to show
+ functions' <literal>LEAKPROOF</> property, if set (Jeevan Chalke)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Remove <application>configure</>'s check prohibiting linking to a
+ threaded <application>libpython</>
+ on <systemitem class="osname">OpenBSD</> (Tom Lane)
+ </para>
+
+ <para>
+ The failure this restriction was meant to prevent seems to not be a
+ problem anymore on current <systemitem class="osname">OpenBSD</>
+ versions.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Allow <application>libpq</> to use TLS protocol versions beyond v1
+ (Noah Misch)
+ </para>
+
+ <para>
+ For a long time, <application>libpq</> was coded so that the only SSL
+ protocol it would allow was TLS v1. Now that newer TLS versions are
+ becoming popular, allow it to negotiate the highest commonly-supported
+ TLS version with the server. (<productname>PostgreSQL</> servers were
+ already capable of such negotiation, so no change is needed on the
+ server side.) This is a back-patch of a change already released in
+ 9.4.0.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-9-2-11">
<title>Release 9.2.11</title>
@@ -215,6 +310,20 @@
</para>
</listitem>
+<!--
+Author: Alvaro Herrera <alvherre@alvh.no-ip.org>
+Branch: REL9_2_STABLE [97ff2a564] 2015-05-18 17:44:21 -0300
+Branch: REL9_1_STABLE [2360eea3b] 2015-05-18 17:44:21 -0300
+Branch: REL9_0_STABLE [850e1a566] 2015-05-18 17:44:21 -0300
+-->
+
+ <listitem>
+ <para>
+ Avoid <quote>cannot GetMultiXactIdMembers() during recovery</> error
+ (Álvaro Herrera)
+ </para>
+ </listitem>
+
<listitem>
<para>
Recursively <function>fsync()</> the data directory after a crash
diff --git a/doc/src/sgml/release-9.3.sgml b/doc/src/sgml/release-9.3.sgml
index 38f3354bd8fcad2500d39d081891bbe610f812f2..8f1bc7e1472d51ae5929c5e424d583332be3345e 100644
--- a/doc/src/sgml/release-9.3.sgml
+++ b/doc/src/sgml/release-9.3.sgml
@@ -1,6 +1,114 @@
<!-- doc/src/sgml/release-9.3.sgml -->
<!-- See header comment in release.sgml about typical markup -->
+ <sect1 id="release-9-3-8">
+ <title>Release 9.3.8</title>
+
+ <note>
+ <title>Release Date</title>
+ <simpara>2015-06-04</simpara>
+ </note>
+
+ <para>
+ This release contains a small number of fixes from 9.3.7.
+ 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.8</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.7,
+ see <xref linkend="release-9-3-7">.
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Avoid failures while <function>fsync</>'ing data directory during
+ crash restart (Abhijit Menon-Sen, Tom Lane)
+ </para>
+
+ <para>
+ In the previous minor releases we added a patch to <function>fsync</>
+ everything in the data directory after a crash. Unfortunately its
+ response to any error condition was to fail, thereby preventing the
+ server from starting up, even when the problem was quite harmless.
+ An example is that an unwritable file in the data directory would
+ prevent restart on some platforms; but it is common to make SSL
+ certificate files unwritable by the server. Revise this behavior so
+ that permissions failures are ignored altogether, and other types of
+ failures are logged but do not prevent continuing.
+ </para>
+
+ <para>
+ Also apply the same rules in <literal>initdb --sync-only</>.
+ This case is less critical but it should act similarly.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix <function>pg_get_functiondef()</> to show
+ functions' <literal>LEAKPROOF</> property, if set (Jeevan Chalke)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Remove <application>configure</>'s check prohibiting linking to a
+ threaded <application>libpython</>
+ on <systemitem class="osname">OpenBSD</> (Tom Lane)
+ </para>
+
+ <para>
+ The failure this restriction was meant to prevent seems to not be a
+ problem anymore on current <systemitem class="osname">OpenBSD</>
+ versions.
+ </para>
+ </listitem>
+
+<!--
+Author: Tom Lane <tgl@sss.pgh.pa.us>
+Branch: REL9_3_STABLE [c6b7b9a9c] 2015-05-21 20:41:55 -0400
+Branch: REL9_2_STABLE [b78fbfe65] 2015-05-21 20:41:55 -0400
+Branch: REL9_1_STABLE [2c2c5f0e0] 2015-05-21 20:41:55 -0400
+Branch: REL9_0_STABLE [4dddf8552] 2015-05-21 20:41:55 -0400
+-->
+
+ <listitem>
+ <para>
+ Allow <application>libpq</> to use TLS protocol versions beyond v1
+ (Noah Misch)
+ </para>
+
+ <para>
+ For a long time, <application>libpq</> was coded so that the only SSL
+ protocol it would allow was TLS v1. Now that newer TLS versions are
+ becoming popular, allow it to negotiate the highest commonly-supported
+ TLS version with the server. (<productname>PostgreSQL</> servers were
+ already capable of such negotiation, so no change is needed on the
+ server side.) This is a back-patch of a change already released in
+ 9.4.0.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-9-3-7">
<title>Release 9.3.7</title>
diff --git a/doc/src/sgml/release-9.4.sgml b/doc/src/sgml/release-9.4.sgml
index e9d1d29aa3cc8eec97dfe098036b42bdec121e2b..a96cd8dce2da764b35a9f16e7596ea688d238d62 100644
--- a/doc/src/sgml/release-9.4.sgml
+++ b/doc/src/sgml/release-9.4.sgml
@@ -1,6 +1,149 @@
<!-- doc/src/sgml/release-9.4.sgml -->
<!-- See header comment in release.sgml about typical markup -->
+ <sect1 id="release-9-4-3">
+ <title>Release 9.4.3</title>
+
+ <note>
+ <title>Release Date</title>
+ <simpara>2015-06-04</simpara>
+ </note>
+
+ <para>
+ This release contains a small number of fixes from 9.4.2.
+ 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.3</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.2,
+ see <xref linkend="release-9-4-2">.
+ </para>
+ </sect2>
+
+ <sect2>
+ <title>Changes</title>
+
+ <itemizedlist>
+
+<!--
+Author: Tom Lane <tgl@sss.pgh.pa.us>
+Branch: master [d8179b001] 2015-05-28 17:33:03 -0400
+Branch: REL9_4_STABLE [a3ae3db43] 2015-05-28 17:33:03 -0400
+Branch: REL9_3_STABLE [81f3d3b7c] 2015-05-28 17:33:03 -0400
+Branch: REL9_2_STABLE [aa8377e64] 2015-05-28 17:33:03 -0400
+Branch: REL9_1_STABLE [cb867853a] 2015-05-28 17:33:03 -0400
+Branch: REL9_0_STABLE [e4a04e5a4] 2015-05-28 17:33:03 -0400
+Author: Tom Lane <tgl@sss.pgh.pa.us>
+Branch: master [c07d8c963] 2015-05-29 13:05:16 -0400
+Branch: REL9_4_STABLE [dbde225b1] 2015-05-29 13:05:16 -0400
+Branch: REL9_3_STABLE [52fc94844] 2015-05-29 13:05:16 -0400
+Author: Tom Lane <tgl@sss.pgh.pa.us>
+Branch: master [57e1138bc] 2015-05-29 15:11:36 -0400
+Branch: REL9_4_STABLE [70a4519b8] 2015-05-29 15:11:36 -0400
+Branch: REL9_3_STABLE [35dd1b51f] 2015-05-29 15:11:36 -0400
+Branch: REL9_2_STABLE [77642a819] 2015-05-29 15:11:36 -0400
+Branch: REL9_1_STABLE [9e79ca326] 2015-05-29 15:11:36 -0400
+Branch: REL9_0_STABLE [bf2f20c08] 2015-05-29 15:11:36 -0400
+Author: Tom Lane <tgl@sss.pgh.pa.us>
+Branch: master [1943c000b] 2015-05-29 17:02:58 -0400
+Branch: REL9_4_STABLE [99f50dd72] 2015-05-29 17:02:58 -0400
+Branch: REL9_3_STABLE [c2b68b1f7] 2015-05-29 17:02:58 -0400
+-->
+
+ <listitem>
+ <para>
+ Avoid failures while <function>fsync</>'ing data directory during
+ crash restart (Abhijit Menon-Sen, Tom Lane)
+ </para>
+
+ <para>
+ In the previous minor releases we added a patch to <function>fsync</>
+ everything in the data directory after a crash. Unfortunately its
+ response to any error condition was to fail, thereby preventing the
+ server from starting up, even when the problem was quite harmless.
+ An example is that an unwritable file in the data directory would
+ prevent restart on some platforms; but it is common to make SSL
+ certificate files unwritable by the server. Revise this behavior so
+ that permissions failures are ignored altogether, and other types of
+ failures are logged but do not prevent continuing.
+ </para>
+
+ <para>
+ Also apply the same rules in <literal>initdb --sync-only</>.
+ This case is less critical but it should act similarly.
+ </para>
+ </listitem>
+
+<!--
+Author: Tom Lane <tgl@sss.pgh.pa.us>
+Branch: master [f46edf479] 2015-05-28 11:24:37 -0400
+Branch: REL9_4_STABLE [d4a9f5519] 2015-05-28 11:24:37 -0400
+Branch: REL9_3_STABLE [27bae8d96] 2015-05-28 11:24:37 -0400
+Branch: REL9_2_STABLE [f3c67aad4] 2015-05-28 11:24:37 -0400
+-->
+
+ <listitem>
+ <para>
+ Fix <function>pg_get_functiondef()</> to show
+ functions' <literal>LEAKPROOF</> property, if set (Jeevan Chalke)
+ </para>
+ </listitem>
+
+<!--
+Author: Andrew Dunstan <andrew@dunslane.net>
+Branch: master [5302760a5] 2015-05-22 10:21:41 -0400
+Branch: REL9_4_STABLE [9b74f32cd] 2015-05-22 10:31:29 -0400
+-->
+
+ <listitem>
+ <para>
+ Fix <function>pushJsonbValue()</> to unpack <type>jbvBinary</>
+ objects (Andrew Dunstan)
+ </para>
+
+ <para>
+ This change does not affect any behavior in the core code as of 9.4,
+ but it avoids a corner case for possible third-party callers.
+ </para>
+ </listitem>
+
+<!--
+Author: Tom Lane <tgl@sss.pgh.pa.us>
+Branch: master [86832eb89] 2015-05-26 22:14:59 -0400
+Branch: REL9_4_STABLE [79f0f7cab] 2015-05-26 22:14:59 -0400
+Branch: REL9_3_STABLE [9e980e7d0] 2015-05-26 22:14:59 -0400
+Branch: REL9_2_STABLE [1b1457120] 2015-05-26 22:14:59 -0400
+Branch: REL9_1_STABLE [5585cc707] 2015-05-26 22:14:59 -0400
+Branch: REL9_0_STABLE [b06649b7f] 2015-05-26 22:15:00 -0400
+-->
+
+ <listitem>
+ <para>
+ Remove <application>configure</>'s check prohibiting linking to a
+ threaded <application>libpython</>
+ on <systemitem class="osname">OpenBSD</> (Tom Lane)
+ </para>
+
+ <para>
+ The failure this restriction was meant to prevent seems to not be a
+ problem anymore on current <systemitem class="osname">OpenBSD</>
+ versions.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
<sect1 id="release-9-4-2">
<title>Release 9.4.2</title>