mirror of
https://github.com/postgres/postgres.git
synced 2025-08-22 21:53:06 +03:00
Minor copy-editing for release note updates.
This commit is contained in:
@@ -1,5 +1,5 @@
|
|||||||
<!--
|
<!--
|
||||||
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.321.4.27 2007/01/05 20:03:19 momjian Exp $
|
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.321.4.28 2007/01/05 22:35:04 tgl Exp $
|
||||||
-->
|
-->
|
||||||
|
|
||||||
<appendix id="release">
|
<appendix id="release">
|
||||||
@@ -44,10 +44,29 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.321.4.27 2007/01/05 20:03:19 mo
|
|||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Fix <quote>failed to re-find parent key</> errors in
|
||||||
|
<command>VACUUM</> (Tom)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Fix race condition for truncation of a large relation across a
|
||||||
|
gigabyte boundary by <command>VACUUM</> (Tom)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Fix bugs affecting multi-gigabyte hash indexes (Tom)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Fix <link linkend="SQL-VACUUM"><command>VACUUM</></link> to recover from
|
Fix possible deadlock in Windows signal handling (Teodor)
|
||||||
a rare problem during index page deletion/split (Tom)
|
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@@ -64,20 +83,6 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.321.4.27 2007/01/05 20:03:19 mo
|
|||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
|
||||||
<para>
|
|
||||||
Fix problem with extending hash indexes that span multiple 1-gigabyte
|
|
||||||
segments (Tom)
|
|
||||||
</para>
|
|
||||||
</listitem>
|
|
||||||
|
|
||||||
<listitem>
|
|
||||||
<para>
|
|
||||||
Fix problem where truncation of a multi-gigabyte table might cause
|
|
||||||
consistency problems with other backends (Tom)
|
|
||||||
</para>
|
|
||||||
</listitem>
|
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
<function>to_number()</> and <function>to_char(numeric)</>
|
<function>to_number()</> and <function>to_char(numeric)</>
|
||||||
@@ -89,22 +94,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.321.4.27 2007/01/05 20:03:19 mo
|
|||||||
<para>
|
<para>
|
||||||
This is because <link
|
This is because <link
|
||||||
linkend="guc-lc-numeric"><varname>lc_numeric</></link> can potentially
|
linkend="guc-lc-numeric"><varname>lc_numeric</></link> can potentially
|
||||||
change the output of the functions.
|
change the output of these functions.
|
||||||
</para>
|
|
||||||
</listitem>
|
|
||||||
|
|
||||||
<listitem>
|
|
||||||
<para>
|
|
||||||
Update timezone database, particularly for Western Australia,
|
|
||||||
which has a new daylight savings date (Tom)
|
|
||||||
</para>
|
|
||||||
</listitem>
|
|
||||||
|
|
||||||
<listitem>
|
|
||||||
<para>
|
|
||||||
Document a risk that if a row is locked inside multiple sub-transactions
|
|
||||||
in the same transaction, and a sub-transaction is rolled back, the row
|
|
||||||
lock is lost (Tom)
|
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@@ -118,6 +108,17 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.321.4.27 2007/01/05 20:03:19 mo
|
|||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Update timezone database
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
This affects Australian and Canadian daylight-savings rules in
|
||||||
|
particular.
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
|
|
||||||
</sect2>
|
</sect2>
|
||||||
@@ -3369,24 +3370,23 @@ typedefs (Michael)</para></listitem>
|
|||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Fix <link linkend="SQL-VACUUM"><command>VACUUM</></link> to recover from
|
Fix <quote>failed to re-find parent key</> errors in
|
||||||
a rare problem during index page deletion/split (Tom)
|
<command>VACUUM</> (Tom)
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Fix bugs affecting multi-gigabyte hash indexes (Tom)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Fix error when constructing an <literal>ARRAY[]</> made up of multiple empty
|
Fix error when constructing an <literal>ARRAY[]</> made up of multiple
|
||||||
elements (Tom)
|
empty elements (Tom)
|
||||||
</para>
|
|
||||||
</listitem>
|
|
||||||
|
|
||||||
<listitem>
|
|
||||||
<para>
|
|
||||||
Fix problem with extending hash indexes that span multiple 1-gigabyte
|
|
||||||
segments (Tom)
|
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@@ -3401,7 +3401,7 @@ typedefs (Michael)</para></listitem>
|
|||||||
<para>
|
<para>
|
||||||
This is because <link
|
This is because <link
|
||||||
linkend="guc-lc-numeric"><varname>lc_numeric</></link> can potentially
|
linkend="guc-lc-numeric"><varname>lc_numeric</></link> can potentially
|
||||||
change the output of the functions.
|
change the output of these functions.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@@ -6418,7 +6418,7 @@ DROP SCHEMA information_schema CASCADE;
|
|||||||
<para>
|
<para>
|
||||||
This is because <link
|
This is because <link
|
||||||
linkend="guc-lc-numeric"><varname>lc_numeric</></link> can potentially
|
linkend="guc-lc-numeric"><varname>lc_numeric</></link> can potentially
|
||||||
change the output of the functions.
|
change the output of these functions.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user