Skip to content

Commit

Permalink
Update release notes for upcoming re-releases.
Browse files Browse the repository at this point in the history
  • Loading branch information
tglsfdc committed May 9, 2005
1 parent cb0ddb6 commit 6a36111
Show file tree
Hide file tree
Showing 2 changed files with 24 additions and 3 deletions.
12 changes: 11 additions & 1 deletion HISTORY
Expand Up @@ -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.
Expand All @@ -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 %
Expand Down
15 changes: 13 additions & 2 deletions doc/src/sgml/release.sgml
@@ -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">
Expand All @@ -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>
Expand All @@ -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
Expand Down

0 comments on commit 6a36111

Please sign in to comment.