Update release notes for upcoming re-releases.
This commit is contained in:
parent
cb0ddb62e2
commit
6a36111eca
12
HISTORY
12
HISTORY
|
@ -3,7 +3,7 @@
|
|||
|
||||
Release 7.2.8
|
||||
|
||||
Release date: 2005-05-05
|
||||
Release date: 2005-05-09
|
||||
|
||||
This release contains a variety of fixes from 7.2.7, including one
|
||||
security-related issue.
|
||||
|
@ -16,6 +16,16 @@
|
|||
|
||||
Changes
|
||||
|
||||
* Repair ancient race condition that allowed a transaction to be
|
||||
seen as committed for some purposes (eg SELECT FOR UPDATE)
|
||||
slightly sooner than for other purposes
|
||||
This is an extremely serious bug since it could lead to apparent
|
||||
data inconsistencies being briefly visible to applications.
|
||||
* Repair race condition between relation extension and VACUUM
|
||||
This could theoretically have caused loss of a page's worth of
|
||||
freshly-inserted data, although the scenario seems of very low
|
||||
probability. There are no known cases of it having caused more
|
||||
than an Assert failure.
|
||||
* Fix EXTRACT(EPOCH) for TIME WITH TIME ZONE values
|
||||
* Additional buffer overrun checks in plpgsql (Neil)
|
||||
* Fix pg_dump to dump index names and trigger names containing %
|
||||
|
|
|
@ -1,5 +1,5 @@
|
|||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.115.2.12 2005/05/05 20:10:06 tgl Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.115.2.13 2005/05/09 00:10:52 tgl Exp $
|
||||
-->
|
||||
|
||||
<appendix id="release">
|
||||
|
@ -10,7 +10,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.115.2.12 2005/05/05 20:10:
|
|||
|
||||
<note>
|
||||
<title>Release date</title>
|
||||
<simpara>2005-05-05</simpara>
|
||||
<simpara>2005-05-09</simpara>
|
||||
</note>
|
||||
|
||||
<para>
|
||||
|
@ -30,6 +30,17 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.115.2.12 2005/05/05 20:10:
|
|||
<title>Changes</title>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para>Repair ancient race condition that allowed a transaction to be
|
||||
seen as committed for some purposes (eg SELECT FOR UPDATE) slightly sooner
|
||||
than for other purposes</para>
|
||||
<para>This is an extremely serious bug since it could lead to apparent
|
||||
data inconsistencies being briefly visible to applications.</para></listitem>
|
||||
<listitem><para>Repair race condition between relation extension and
|
||||
VACUUM</para>
|
||||
<para>This could theoretically have caused loss of a page's worth of
|
||||
freshly-inserted data, although the scenario seems of very low probability.
|
||||
There are no known cases of it having caused more than an Assert failure.
|
||||
</para></listitem>
|
||||
<listitem><para>Fix <function>EXTRACT(EPOCH)</> for
|
||||
<type>TIME WITH TIME ZONE</> values</para></listitem>
|
||||
<listitem><para>Additional buffer overrun checks in plpgsql
|
||||
|
|
Loading…
Reference in New Issue