summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane2005-05-09 00:10:35 +0000
committerTom Lane2005-05-09 00:10:35 +0000
commite5921b3230f175669faf4b97cd967a2dd5023fdc (patch)
tree32657d6e6e7afadf035cb8d4d3e549cc26d2ce35
parentdc9e82d0e605f4c708bad26102924be581d9c8ca (diff)
Update release notes for upcoming re-releases.REL7_3_10
-rw-r--r--doc/src/sgml/release.sgml28
1 files changed, 25 insertions, 3 deletions
diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml
index 5f9870b4382..efe527db21a 100644
--- a/doc/src/sgml/release.sgml
+++ b/doc/src/sgml/release.sgml
@@ -1,5 +1,5 @@
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.163.2.21 2005/05/05 20:09:11 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.163.2.22 2005/05/09 00:10:35 tgl Exp $
-->
<appendix id="release">
@@ -10,7 +10,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.163.2.21 2005/05/05 20:09:
<note>
<title>Release date</title>
- <simpara>2005-05-05</simpara>
+ <simpara>2005-05-09</simpara>
</note>
<para>
@@ -87,6 +87,17 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
<itemizedlist>
<listitem><para>Change encoding function signature to prevent
misuse</para></listitem>
+<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 comparisons of <type>TIME WITH TIME ZONE</> values</para>
<para>
The comparison code was wrong in the case where the
@@ -1286,7 +1297,7 @@ operations on bytea columns (Joe)</para></listitem>
<note>
<title>Release date</title>
- <simpara>2005-05-05</simpara>
+ <simpara>2005-05-09</simpara>
</note>
<para>
@@ -1306,6 +1317,17 @@ operations on bytea columns (Joe)</para></listitem>
<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