Skip to content

P
Postgres FD Implementation
Commit 551fb5ac authored by Tom Lane's avatar Tom Lane
Browse files
Options

Release notes for 9.3.4, 9.2.8, 9.1.13, 9.0.17, 8.4.21.

parent d70cf811
Hide whitespace changes
Inline Side-by-side
Showing with 703 additions and 33 deletions
doc/src/sgml/release-8.4.sgml
View file @ 551fb5ac
<!-- doc/src/sgml/release-8.4.sgml --> <!-- doc/src/sgml/release-8.4.sgml -->
<!-- See header comment in release.sgml about typical markup --> <!-- 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</> 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</> 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</> when de-parsing a
rule or view (Dean Rasheed)
</para>
<para>
This oversight resulted in <application>pg_dump</> unexpectedly
acquiring <literal>RowExclusiveLock</> locks on tables mentioned as
the targets of <literal>INSERT</>/<literal>UPDATE</>/<literal>DELETE</>
commands in rules. While usually harmless, that could interfere with
concurrent transactions that tried to acquire, for example,
<literal>ShareLock</> on those tables.
</para>
</listitem>
<listitem>
<para>
Prevent interrupts while reporting non-<literal>ERROR</> messages
(Tom Lane)
</para>
<para>
This guards against rare server-process freezeups due to recursive
entry to <function>syslog()</>, and perhaps other related problems.
</para>
</listitem>
<listitem>
<para>
Update time zone data files to <application>tzdata</> 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"> <sect1 id="release-8-4-20">
<title>Release 8.4.20</title> <title>Release 8.4.20</title>
......
doc/src/sgml/release-9.0.sgml
View file @ 551fb5ac
<!-- doc/src/sgml/release-9.0.sgml --> <!-- doc/src/sgml/release-9.0.sgml -->
<!-- See header comment in release.sgml about typical markup --> <!-- 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</> 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</> 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</> when de-parsing a
rule or view (Dean Rasheed)
</para>
<para>
This oversight resulted in <application>pg_dump</> unexpectedly
acquiring <literal>RowExclusiveLock</> locks on tables mentioned as
the targets of <literal>INSERT</>/<literal>UPDATE</>/<literal>DELETE</>
commands in rules. While usually harmless, that could interfere with
concurrent transactions that tried to acquire, for example,
<literal>ShareLock</> 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</> messages
(Tom Lane)
</para>
<para>
This guards against rare server-process freezeups due to recursive
entry to <function>syslog()</>, and perhaps other related problems.
</para>
</listitem>
<listitem>
<para>
Prevent intermittent <quote>could not reserve shared memory region</>
failures on recent Windows versions (MauMau)
</para>
</listitem>
<listitem>
<para>
Update time zone data files to <application>tzdata</> 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"> <sect1 id="release-9-0-16">
<title>Release 9.0.16</title> <title>Release 9.0.16</title>
......
doc/src/sgml/release-9.1.sgml
View file @ 551fb5ac
<!-- doc/src/sgml/release-9.1.sgml --> <!-- doc/src/sgml/release-9.1.sgml -->
<!-- See header comment in release.sgml about typical markup --> <!-- See header comment in release.sgml about typical markup -->
<sect1 id="release-9-1-13">
<title>Release 9.1.13</title>
<note>
<title>Release Date</title>
<simpara>2014-03-20</simpara>
</note>
<para>
This release contains a variety of fixes from 9.1.12.
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.13</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.11,
see <xref linkend="release-9-1-11">.
</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</> 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</> 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</> when de-parsing a
rule or view (Dean Rasheed)
</para>
<para>
This oversight resulted in <application>pg_dump</> unexpectedly
acquiring <literal>RowExclusiveLock</> locks on tables mentioned as
the targets of <literal>INSERT</>/<literal>UPDATE</>/<literal>DELETE</>
commands in rules. While usually harmless, that could interfere with
concurrent transactions that tried to acquire, for example,
<literal>ShareLock</> 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 <application>walsender</>'s failure to shut down cleanly when client
is <application>pg_receivexlog</> (Fujii Masao)
</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</> messages
(Tom Lane)
</para>
<para>
This guards against rare server-process freezeups due to recursive
entry to <function>syslog()</>, and perhaps other related problems.
</para>
</listitem>
<listitem>
<para>
Fix memory leak in PL/Perl when returning a composite result, including
multiple-OUT-parameter cases (Alex Hunsaker)
</para>
</listitem>
<listitem>
<para>
Prevent intermittent <quote>could not reserve shared memory region</>
failures on recent Windows versions (MauMau)
</para>
</listitem>
<listitem>
<para>
Update time zone data files to <application>tzdata</> 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-1-12"> <sect1 id="release-9-1-12">
<title>Release 9.1.12</title> <title>Release 9.1.12</title>
......
doc/src/sgml/release-9.2.sgml
View file @ 551fb5ac
<!-- doc/src/sgml/release-9.2.sgml --> <!-- doc/src/sgml/release-9.2.sgml -->
<!-- See header comment in release.sgml about typical markup --> <!-- See header comment in release.sgml about typical markup -->
<sect1 id="release-9-2-8">
<title>Release 9.2.8</title>
<note>
<title>Release Date</title>
<simpara>2014-03-20</simpara>
</note>
<para>
This release contains a variety of fixes from 9.2.7.
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.8</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.6,
see <xref linkend="release-9-2-6">.
</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</> 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</> 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</> when de-parsing a
rule or view (Dean Rasheed)
</para>
<para>
This oversight resulted in <application>pg_dump</> unexpectedly
acquiring <literal>RowExclusiveLock</> locks on tables mentioned as
the targets of <literal>INSERT</>/<literal>UPDATE</>/<literal>DELETE</>
commands in rules. While usually harmless, that could interfere with
concurrent transactions that tried to acquire, for example,
<literal>ShareLock</> 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 <application>walsender</>'s failure to shut down cleanly when client
is <application>pg_receivexlog</> (Fujii Masao)
</para>
</listitem>
<listitem>
<para>
Check WAL level and hot standby parameters correctly when doing crash
recovery that will be followed by archive recovery (Heikki Linnakangas)
</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</> messages
(Tom Lane)
</para>
<para>
This guards against rare server-process freezeups due to recursive
entry to <function>syslog()</>, and perhaps other related problems.
</para>
</listitem>
<listitem>
<para>
Fix memory leak in PL/Perl when returning a composite result, including
multiple-OUT-parameter cases (Alex Hunsaker)
</para>
</listitem>
<listitem>
<para>
Fix tracking of <application>psql</> script line numbers
during <literal>\copy</> from out-of-line data
(Kumar Rajeev Rastogi, Amit Khandekar)
</para>
<para>
<literal>\copy ... from</> incremented the script file line number
for each data line, even if the data was not coming from the script
file. This mistake resulted in wrong line numbers being reported for
any errors occurring later in the same script file.
</para>
</listitem>
<listitem>
<para>
Prevent intermittent <quote>could not reserve shared memory region</>
failures on recent Windows versions (MauMau)
</para>
</listitem>
<listitem>
<para>
Update time zone data files to <application>tzdata</> 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-2-7"> <sect1 id="release-9-2-7">
<title>Release 9.2.7</title> <title>Release 9.2.7</title>
......
doc/src/sgml/release-9.3.sgml
View file @ 551fb5ac
...@@ -29,18 +29,6 @@ ...@@ -29,18 +29,6 @@
this update. this update.
</para> </para>
<para>
Also, the error fixed in the second changelog entry below could have
caused some bloat in statistics data. Users who have done
many <command>DROP DATABASE</> commands since upgrading to 9.3 may wish
to manually remove files in <filename>$PGDATA/pg_stat_tmp</>
(or <filename>$PGDATA/pg_stat</> if the server is not running) that
have old modification times and do not correspond to any database OID
present in <filename>$PGDATA/base</>. If you do this, note that the
file <filename>db_0.stat</> is a valid file even though it does not
correspond to any <filename>$PGDATA/base</> subdirectory.
</para>
<para> <para>
Also, if you are upgrading from a version earlier than 9.3.3, Also, if you are upgrading from a version earlier than 9.3.3,
see <xref linkend="release-9-3-3">. see <xref linkend="release-9-3-3">.
...@@ -66,27 +54,15 @@ Branch: REL9_3_STABLE [9a57858f1] 2014-02-27 11:23:24 -0300 ...@@ -66,27 +54,15 @@ Branch: REL9_3_STABLE [9a57858f1] 2014-02-27 11:23:24 -0300
</para> </para>
<para> <para>
This error allowed multiple versions of the same row to become This error caused updated rows to not be found by index scans, resulting
visible to queries, resulting in apparent duplicates. Since the in inconsistent query results depending on whether an index scan was
error is in WAL replay, it would only manifest during crash recovery used. Subsequent processing could result in constraint violations,
or on standby servers. since the previously updated row would not be found by later index
</para> searches, thus possibly allowing conflicting rows to be inserted.
</listitem> Since this error is in WAL replay, it would only manifest during crash
recovery or on standby servers. The improperly-replayed case most
<!-- commonly arises when a table row that is referenced by a foreign-key
Author: Alvaro Herrera <alvherre@alvh.no-ip.org> constraint is updated concurrently with creation of a referencing row.
Branch: master [2b4f2ab33] 2014-03-05 13:03:29 -0300
Branch: REL9_3_STABLE [13ea43ab8] 2014-03-05 13:03:29 -0300
-->
<listitem>
<para>
Remove the correct per-database statistics file during <command>DROP
DATABASE</> (Tomas Vondra)
</para>
<para>
This fix prevents a permanent leak of statistics file space.
</para> </para>
</listitem> </listitem>
...@@ -263,6 +239,28 @@ Branch: REL9_3_STABLE [e8655a77f] 2014-02-21 17:10:49 -0500 ...@@ -263,6 +239,28 @@ Branch: REL9_3_STABLE [e8655a77f] 2014-02-21 17:10:49 -0500
</para> </para>
</listitem> </listitem>
<!--
Author: Alvaro Herrera <alvherre@alvh.no-ip.org>
Branch: master [2b4f2ab33] 2014-03-05 13:03:29 -0300
Branch: REL9_3_STABLE [13ea43ab8] 2014-03-05 13:03:29 -0300
-->
<listitem>
<para>
Remove the correct per-database statistics file during <command>DROP
DATABASE</> (Tomas Vondra)
</para>
<para>
This fix prevents a permanent leak of statistics file space.
Users who have done many <command>DROP DATABASE</> commands since
upgrading to <productname>PostgreSQL</> 9.3 may wish to check their
statistics directory and delete statistics files that do not
correspond to any existing database. Please note
that <filename>db_0.stat</> should not be removed.
</para>
</listitem>
<!-- <!--
Author: Heikki Linnakangas <heikki.linnakangas@iki.fi> Author: Heikki Linnakangas <heikki.linnakangas@iki.fi>
Branch: master [94ae6ba74] 2014-03-06 21:38:51 +0200 Branch: master [94ae6ba74] 2014-03-06 21:38:51 +0200
...@@ -283,6 +281,21 @@ Branch: REL9_3_STABLE [dcd1131c8] 2014-03-06 21:40:50 +0200 ...@@ -283,6 +281,21 @@ Branch: REL9_3_STABLE [dcd1131c8] 2014-03-06 21:40:50 +0200
</para> </para>
</listitem> </listitem>
<!--
Author: Fujii Masao <fujii@postgresql.org>
Branch: master [5c6d9fc4b] 2014-03-17 20:37:50 +0900
Branch: REL9_3_STABLE [385723405] 2014-03-17 20:41:12 +0900
Branch: REL9_2_STABLE [7899aa356] 2014-03-17 20:41:52 +0900
Branch: REL9_1_STABLE [65e8dbb18] 2014-03-17 20:42:35 +0900
-->
<listitem>
<para>
Fix <application>walsender</>'s failure to shut down cleanly when client
is <application>pg_receivexlog</> (Fujii Masao)
</para>
</listitem>
<!-- <!--
Author: Heikki Linnakangas <heikki.linnakangas@iki.fi> Author: Heikki Linnakangas <heikki.linnakangas@iki.fi>
Branch: master [956685f82] 2014-03-05 14:48:14 +0200 Branch: master [956685f82] 2014-03-05 14:48:14 +0200
...@@ -352,6 +365,21 @@ Branch: REL8_4_STABLE [172c53e92] 2014-03-13 20:59:57 -0400 ...@@ -352,6 +365,21 @@ Branch: REL8_4_STABLE [172c53e92] 2014-03-13 20:59:57 -0400
</para> </para>
</listitem> </listitem>
<!--
Author: Alvaro Herrera <alvherre@alvh.no-ip.org>
Branch: master [bd1154ede] 2014-03-16 23:22:21 -0300
Branch: REL9_3_STABLE [60829079d] 2014-03-16 23:22:22 -0300
Branch: REL9_2_STABLE [ba5946e86] 2014-03-16 23:22:22 -0300
Branch: REL9_1_STABLE [f84997c7e] 2014-03-16 23:22:22 -0300
-->
<listitem>
<para>
Fix memory leak in PL/Perl when returning a composite result, including
multiple-OUT-parameter cases (Alex Hunsaker)
</para>
</listitem>
<!-- <!--
Author: Tom Lane <tgl@sss.pgh.pa.us> Author: Tom Lane <tgl@sss.pgh.pa.us>
Branch: master [e85a5ffba] 2014-03-10 15:47:40 -0400 Branch: master [e85a5ffba] 2014-03-10 15:47:40 -0400
...@@ -401,6 +429,8 @@ Author: Magnus Hagander <magnus@hagander.net> ...@@ -401,6 +429,8 @@ Author: Magnus Hagander <magnus@hagander.net>
Branch: master [7f3e17b48] 2014-02-18 14:45:58 +0100 Branch: master [7f3e17b48] 2014-02-18 14:45:58 +0100
Branch: REL9_3_STABLE [b88ecb002] 2014-02-18 14:49:41 +0100 Branch: REL9_3_STABLE [b88ecb002] 2014-02-18 14:49:41 +0100
Branch: REL9_2_STABLE [062deb313] 2014-02-18 14:50:19 +0100 Branch: REL9_2_STABLE [062deb313] 2014-02-18 14:50:19 +0100
Branch: REL9_1_STABLE [fae12f331] 2014-03-16 11:46:20 +0100
Branch: REL9_0_STABLE [665515539] 2014-03-16 11:47:37 +0100
--> -->
<listitem> <listitem>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment