diff options
| -rw-r--r-- | doc/src/sgml/release-9.0.sgml | 101 | ||||
| -rw-r--r-- | doc/src/sgml/release-9.1.sgml | 95 | ||||
| -rw-r--r-- | doc/src/sgml/release-9.2.sgml | 109 | ||||
| -rw-r--r-- | doc/src/sgml/release-9.3.sgml | 108 |
4 files changed, 413 insertions, 0 deletions
diff --git a/doc/src/sgml/release-9.0.sgml b/doc/src/sgml/release-9.0.sgml index 9794b5b3b76..80cd1c43cdc 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> @@ -171,6 +265,13 @@ <listitem> <para> + Avoid <quote>cannot GetMultiXactIdMembers() during recovery</> error + (Álvaro Herrera) + </para> + </listitem> + + <listitem> + <para> Recursively <function>fsync()</> the data directory after a crash (Abhijit Menon-Sen, Robert Haas) </para> diff --git a/doc/src/sgml/release-9.1.sgml b/doc/src/sgml/release-9.1.sgml index f6c0d131576..8306cfab039 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> @@ -203,6 +291,13 @@ <listitem> <para> + Avoid <quote>cannot GetMultiXactIdMembers() during recovery</> error + (Álvaro Herrera) + </para> + </listitem> + + <listitem> + <para> Recursively <function>fsync()</> the data directory after a crash (Abhijit Menon-Sen, Robert Haas) </para> diff --git a/doc/src/sgml/release-9.2.sgml b/doc/src/sgml/release-9.2.sgml index 168a387d345..ef4ce98e538 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 38f3354bd8f..8f1bc7e1472 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> |