Skip to content

Commit

Permalink
Mise à jour en version 9.2.8
Browse files Browse the repository at this point in the history
  • Loading branch information
@gleu
gleu committed Mar 22, 2014
1 parent e6c30a2 commit 64d092d
Show file tree
Hide file tree
Showing 6 changed files with 642 additions and 2 deletions.
2 changes: 1 addition & 1 deletion postgresql/config.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -3674,7 +3674,7 @@ local0.* /var/log/postgresql
<term><varname>syslog_ident</varname> (<type>string</type>)</term>
<listitem>
<indexterm>
<primary>paramètre de configuration <varname>syslog_identity</varname></primary>
<primary>paramètre de configuration <varname>syslog_ident</varname></primary>
</indexterm>
<para>
Si <application>syslog</application> est activé, ce paramètre fixe le nom
Expand Down
122 changes: 122 additions & 0 deletions postgresql/release-8.4.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,128 @@
<!-- doc/src/sgml/release-8.4.sgml -->
<!-- See header comment in release.sgml about typical markup -->

<sect1 id="release-8-4-21">
<title>Release 8.4.21</title>

<note>
<title>Release Date</title>
<simpara>2014-03-20</simpara>
</note>

<para>
This release contains a variety of fixes from 8.4.20.
For information about new features in the 8.4 major release, see
<xref linkend="release-8-4"/>.
</para>

<para>
The <productname>PostgreSQL</productname> community will stop releasing updates
for the 8.4.X release series in July 2014.
Users are encouraged to update to a newer release branch soon.
</para>

<sect2>
<title>Migration to Version 8.4.21</title>

<para>
A dump/restore is not required for those running 8.4.X.
</para>

<para>
However, if you are upgrading from a version earlier than 8.4.19,
see <xref linkend="release-8-4-19"/>.
</para>

</sect2>

<sect2>
<title>Changes</title>

<itemizedlist>

<listitem>
<para>
Restore GIN metapages unconditionally to avoid torn-page risk
(Heikki Linnakangas)
</para>

<para>
Although this oversight could theoretically result in a corrupted
index, it is unlikely to have caused any problems in practice, since
the active part of a GIN metapage is smaller than a standard 512-byte
disk sector.
</para>
</listitem>

<listitem>
<para>
Allow regular-expression operators to be terminated early by query
cancel requests (Tom Lane)
</para>

<para>
This prevents scenarios wherein a pathological regular expression
could lock up a server process uninterruptably for a long time.
</para>
</listitem>

<listitem>
<para>
Remove incorrect code that tried to allow <literal>OVERLAPS</literal> with
single-element row arguments (Joshua Yanovski)
</para>

<para>
This code never worked correctly, and since the case is neither
specified by the SQL standard nor documented, it seemed better to
remove it than fix it.
</para>
</listitem>

<listitem>
<para>
Avoid getting more than <literal>AccessShareLock</literal> when de-parsing a
rule or view (Dean Rasheed)
</para>

<para>
This oversight resulted in <application>pg_dump</application> unexpectedly
acquiring <literal>RowExclusiveLock</literal> locks on tables mentioned as
the targets of <literal>INSERT</literal>/<literal>UPDATE</literal>/<literal>DELETE</literal>
commands in rules. While usually harmless, that could interfere with
concurrent transactions that tried to acquire, for example,
<literal>ShareLock</literal> on those tables.
</para>
</listitem>

<listitem>
<para>
Prevent interrupts while reporting non-<literal>ERROR</literal> messages
(Tom Lane)
</para>

<para>
This guards against rare server-process freezeups due to recursive
entry to <function>syslog()</function>, and perhaps other related problems.
</para>
</listitem>

<listitem>
<para>
Update time zone data files to <application>tzdata</application> release 2014a
for DST law changes in Fiji and Turkey, plus historical changes in
Israel and Ukraine.
</para>

<para>
</para>
</listitem>

</itemizedlist>

</sect2>
</sect1>

<sect1 id="release-8-4-20">
<title>Release 8.4.20</title>

Expand Down
156 changes: 156 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,162 @@
<!-- doc/src/sgml/release-9.0.sgml -->
<!-- See header comment in release.sgml about typical markup -->

<sect1 id="release-9-0-17">
<title>Release 9.0.17</title>

<note>
<title>Release Date</title>
<simpara>2014-03-20</simpara>
</note>

<para>
This release contains a variety of fixes from 9.0.16.
For information about new features in the 9.0 major release, see
<xref linkend="release-9-0"/>.
</para>

<sect2>
<title>Migration to Version 9.0.17</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.15,
see <xref linkend="release-9-0-15"/>.
</para>

</sect2>

<sect2>
<title>Changes</title>

<itemizedlist>

<listitem>
<para>
Restore GIN metapages unconditionally to avoid torn-page risk
(Heikki Linnakangas)
</para>

<para>
Although this oversight could theoretically result in a corrupted
index, it is unlikely to have caused any problems in practice, since
the active part of a GIN metapage is smaller than a standard 512-byte
disk sector.
</para>
</listitem>

<listitem>
<para>
Avoid race condition in checking transaction commit status during
receipt of a <command>NOTIFY</command> message (Marko Tiikkaja)
</para>

<para>
This prevents a scenario wherein a sufficiently fast client might
respond to a notification before database updates made by the
notifier have become visible to the recipient.
</para>
</listitem>

<listitem>
<para>
Allow regular-expression operators to be terminated early by query
cancel requests (Tom Lane)
</para>

<para>
This prevents scenarios wherein a pathological regular expression
could lock up a server process uninterruptably for a long time.
</para>
</listitem>

<listitem>
<para>
Remove incorrect code that tried to allow <literal>OVERLAPS</literal> with
single-element row arguments (Joshua Yanovski)
</para>

<para>
This code never worked correctly, and since the case is neither
specified by the SQL standard nor documented, it seemed better to
remove it than fix it.
</para>
</listitem>

<listitem>
<para>
Avoid getting more than <literal>AccessShareLock</literal> when de-parsing a
rule or view (Dean Rasheed)
</para>

<para>
This oversight resulted in <application>pg_dump</application> unexpectedly
acquiring <literal>RowExclusiveLock</literal> locks on tables mentioned as
the targets of <literal>INSERT</literal>/<literal>UPDATE</literal>/<literal>DELETE</literal>
commands in rules. While usually harmless, that could interfere with
concurrent transactions that tried to acquire, for example,
<literal>ShareLock</literal> on those tables.
</para>
</listitem>

<listitem>
<para>
Improve performance of index endpoint probes during planning (Tom Lane)
</para>

<para>
This change fixes a significant performance problem that occurred
when there were many not-yet-committed rows at the end of the index,
which is a common situation for indexes on sequentially-assigned
values such as timestamps or sequence-generated identifiers.
</para>
</listitem>

<listitem>
<para>
Fix test to see if hot standby connections can be allowed immediately
after a crash (Heikki Linnakangas)
</para>
</listitem>

<listitem>
<para>
Prevent interrupts while reporting non-<literal>ERROR</literal> messages
(Tom Lane)
</para>

<para>
This guards against rare server-process freezeups due to recursive
entry to <function>syslog()</function>, and perhaps other related problems.
</para>
</listitem>

<listitem>
<para>
Prevent intermittent <quote>could not reserve shared memory region</quote>
failures on recent Windows versions (MauMau)
</para>
</listitem>

<listitem>
<para>
Update time zone data files to <application>tzdata</application> release 2014a
for DST law changes in Fiji and Turkey, plus historical changes in
Israel and Ukraine.
</para>

<para>
</para>
</listitem>

</itemizedlist>

</sect2>
</sect1>

<sect1 id="release-9-0-16">
<title>Release 9.0.16</title>

Expand Down

0 comments on commit 64d092d

Please sign in to comment.