Skip to content

Commit

Permalink
Mise à jour en version 9.2.13
Browse files Browse the repository at this point in the history
  • Loading branch information
gleu committed Jun 22, 2015
1 parent 44176f4 commit aa1863d
Show file tree
Hide file tree
Showing 4 changed files with 211 additions and 1 deletion.
74 changes: 74 additions & 0 deletions postgresql/release-9.0.xml
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,80 @@
<!-- doc/src/sgml/release-9.0.sgml -->
<!-- See header comment in release.sgml about typical markup -->

<sect1 id="release-9-0-22">
<title>Release 9.0.22</title>

<note>
<title>Release Date</title>
<simpara>2015-06-12</simpara>
</note>

<para>
This release contains a small number of fixes from 9.0.21.
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.22</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>
Fix rare failure to invalidate relation cache init file (Tom Lane)
</para>

<para>
With just the wrong timing of concurrent activity, a <command>VACUUM
FULL</command> on a system catalog might fail to update the <quote>init file</quote>
that's used to avoid cache-loading work for new sessions. This would
result in later sessions being unable to access that catalog at all.
This is a very ancient bug, but it's so hard to trigger that no
reproducible case had been seen until recently.
</para>
</listitem>

<listitem>
<para>
Avoid deadlock between incoming sessions and <literal>CREATE/DROP
DATABASE</literal> (Tom Lane)
</para>

<para>
A new session starting in a database that is the target of
a <command>DROP DATABASE</command> command, or is the template for
a <command>CREATE DATABASE</command> command, could cause the command to wait
for five seconds and then fail, even if the new session would have
exited before that.
</para>
</listitem>

</itemizedlist>

</sect2>
</sect1>

<sect1 id="release-9-0-21">
<title>Release 9.0.21</title>

Expand Down
68 changes: 68 additions & 0 deletions postgresql/release-9.1.xml
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,74 @@
<!-- doc/src/sgml/release-9.1.sgml -->
<!-- See header comment in release.sgml about typical markup -->

<sect1 id="release-9-1-18">
<title>Release 9.1.18</title>

<note>
<title>Release Date</title>
<simpara>2015-06-12</simpara>
</note>

<para>
This release contains a small number of fixes from 9.1.17.
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.18</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>
Fix rare failure to invalidate relation cache init file (Tom Lane)
</para>

<para>
With just the wrong timing of concurrent activity, a <command>VACUUM
FULL</command> on a system catalog might fail to update the <quote>init file</quote>
that's used to avoid cache-loading work for new sessions. This would
result in later sessions being unable to access that catalog at all.
This is a very ancient bug, but it's so hard to trigger that no
reproducible case had been seen until recently.
</para>
</listitem>

<listitem>
<para>
Avoid deadlock between incoming sessions and <literal>CREATE/DROP
DATABASE</literal> (Tom Lane)
</para>

<para>
A new session starting in a database that is the target of
a <command>DROP DATABASE</command> command, or is the template for
a <command>CREATE DATABASE</command> command, could cause the command to wait
for five seconds and then fail, even if the new session would have
exited before that.
</para>
</listitem>

</itemizedlist>

</sect2>
</sect1>

<sect1 id="release-9-1-17">
<title>Release 9.1.17</title>

Expand Down
68 changes: 68 additions & 0 deletions postgresql/release-9.2.xml
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,74 @@
<!-- doc/src/sgml/release-9.2.sgml -->
<!-- See header comment in release.sgml about typical markup -->

<sect1 id="release-9-2-13">
<title>Release 9.2.13</title>

<note>
<title>Release Date</title>
<simpara>2015-06-12</simpara>
</note>

<para>
This release contains a small number of fixes from 9.2.12.
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.13</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>
Fix rare failure to invalidate relation cache init file (Tom Lane)
</para>

<para>
With just the wrong timing of concurrent activity, a <command>VACUUM
FULL</command> on a system catalog might fail to update the <quote>init file</quote>
that's used to avoid cache-loading work for new sessions. This would
result in later sessions being unable to access that catalog at all.
This is a very ancient bug, but it's so hard to trigger that no
reproducible case had been seen until recently.
</para>
</listitem>

<listitem>
<para>
Avoid deadlock between incoming sessions and <literal>CREATE/DROP
DATABASE</literal> (Tom Lane)
</para>

<para>
A new session starting in a database that is the target of
a <command>DROP DATABASE</command> command, or is the template for
a <command>CREATE DATABASE</command> command, could cause the command to wait
for five seconds and then fail, even if the new session would have
exited before that.
</para>
</listitem>

</itemizedlist>

</sect2>
</sect1>

<sect1 id="release-9-2-12">
<title>Release 9.2.12</title>

Expand Down
2 changes: 1 addition & 1 deletion postgresql/version.xml
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
<!ENTITY version "9.2.12">
<!ENTITY version "9.2.13">
<!ENTITY majorversion "9.2">

0 comments on commit aa1863d

Please sign in to comment.