Skip to content

Commit

Permalink
Mise à jour en version 9.2.12
Browse files Browse the repository at this point in the history
  • Loading branch information
@gleu
gleu committed Jun 5, 2015
1 parent 65afe72 commit 44176f4
Show file tree
Hide file tree
Showing 4 changed files with 306 additions and 1 deletion.
101 changes: 101 additions & 0 deletions postgresql/release-9.0.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,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</productname> 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</function>'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</function>
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</application>'s check prohibiting linking to a
threaded <application>libpython</application>
on <systemitem class="osname">OpenBSD</systemitem> (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</systemitem>
versions.
</para>
</listitem>

<listitem>
<para>
Allow <application>libpq</application> to use TLS protocol versions beyond v1
(Noah Misch)
</para>

<para>
For a long time, <application>libpq</application> 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</productname> 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>

Expand Down Expand Up @@ -170,6 +264,13 @@
</para>
</listitem>

<listitem>
<para>
Avoid <quote>cannot GetMultiXactIdMembers() during recovery</quote> error
(&Aacute;lvaro Herrera)
</para>
</listitem>

<listitem>
<para>
Recursively <function>fsync()</function> the data directory after a crash
Expand Down
95 changes: 95 additions & 0 deletions postgresql/release-9.1.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,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</function>'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</function>
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</application>'s check prohibiting linking to a
threaded <application>libpython</application>
on <systemitem class="osname">OpenBSD</systemitem> (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</systemitem>
versions.
</para>
</listitem>

<listitem>
<para>
Allow <application>libpq</application> to use TLS protocol versions beyond v1
(Noah Misch)
</para>

<para>
For a long time, <application>libpq</application> 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</productname> 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>

Expand Down Expand Up @@ -202,6 +290,13 @@
</para>
</listitem>

<listitem>
<para>
Avoid <quote>cannot GetMultiXactIdMembers() during recovery</quote> error
(&Aacute;lvaro Herrera)
</para>
</listitem>

<listitem>
<para>
Recursively <function>fsync()</function> the data directory after a crash
Expand Down
109 changes: 109 additions & 0 deletions postgresql/release-9.2.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,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</function>'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</function>
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()</function> to show
functions' <literal>LEAKPROOF</literal> property, if set (Jeevan Chalke)
</para>
</listitem>

<listitem>
<para>
Remove <application>configure</application>'s check prohibiting linking to a
threaded <application>libpython</application>
on <systemitem class="osname">OpenBSD</systemitem> (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</systemitem>
versions.
</para>
</listitem>

<listitem>
<para>
Allow <application>libpq</application> to use TLS protocol versions beyond v1
(Noah Misch)
</para>

<para>
For a long time, <application>libpq</application> 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</productname> 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>

Expand Down Expand Up @@ -216,6 +311,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</quote> error
(&Aacute;lvaro Herrera)
</para>
</listitem>

<listitem>
<para>
Recursively <function>fsync()</function> the data directory after a crash
Expand Down
2 changes: 1 addition & 1 deletion postgresql/version.xml
View file
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
<!ENTITY version "9.2.11">
<!ENTITY version "9.2.12">
<!ENTITY majorversion "9.2">

0 comments on commit 44176f4

Please sign in to comment.