A little bit more copy-editing...

This commit is contained in:
Tom Lane 2003-11-15 20:01:11 +00:00
parent c76037aa50
commit 3e9a86a38d

View File

@ -1,5 +1,5 @@
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.241 2003/11/15 01:16:37 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.242 2003/11/15 20:01:11 tgl Exp $
--> -->
<appendix id="release"> <appendix id="release">
@ -113,7 +113,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.241 2003/11/15 01:16:37 pe
<para> <para>
Simple SQL functions can now be inlined by including their SQL Simple SQL functions can now be inlined by including their SQL
in the main query. This improves performance by eliminating in the main query. This improves performance by eliminating
per-call overhead. That means, simple SQL functions now per-call overhead. That means simple SQL functions now
behave like macros. behave like macros.
</para> </para>
</listitem> </listitem>
@ -149,7 +149,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.241 2003/11/15 01:16:37 pe
<varlistentry> <varlistentry>
<term> <term>
Make free space map to efficiently reuse empty index pages, Make free space map efficiently reuse empty index pages,
and other free space management improvements and other free space management improvements
</term> </term>
@ -157,7 +157,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.241 2003/11/15 01:16:37 pe
<para> <para>
In previous releases, B-tree index pages that were left empty In previous releases, B-tree index pages that were left empty
because of deleted rows could only be reused by rows with because of deleted rows could only be reused by rows with
index values similar to the original rows indexed on that index values similar to the rows originally indexed on that
page. In 7.4, <command>VACUUM</command> records empty index page. In 7.4, <command>VACUUM</command> records empty index
pages and allows them to be reused for any future index rows. pages and allows them to be reused for any future index rows.
</para> </para>
@ -180,7 +180,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.241 2003/11/15 01:16:37 pe
<varlistentry> <varlistentry>
<term> <term>
Cursors conform more closely with the SQL standard Cursors conform more closely to the SQL standard
</term> </term>
<listitem> <listitem>
@ -199,7 +199,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.241 2003/11/15 01:16:37 pe
<listitem> <listitem>
<para> <para>
These cursors are also called holdable cursors These cursors are also called holdable cursors.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
@ -315,7 +315,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.241 2003/11/15 01:16:37 pe
release. Significant effort was invested to make the messages release. Significant effort was invested to make the messages
more consistent and user-oriented. If your applications try to more consistent and user-oriented. If your applications try to
detect different error conditions by parsing the error message, detect different error conditions by parsing the error message,
you are strongly encourage to use the new error code facility. you are strongly encouraged to use the new error code facility instead.
</para> </para>
</listitem> </listitem>
@ -568,8 +568,8 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.241 2003/11/15 01:16:37 pe
<listitem> <listitem>
<para>Improve GEQO optimizer performance (Tom)</para> <para>Improve GEQO optimizer performance (Tom)</para>
<para> <para>
There were several inefficiencies in the way the GEQO optimizer This release fixes several inefficiencies in the way the GEQO optimizer
managed potential query paths. This release fixes this. manages potential query paths.
</para> </para>
</listitem> </listitem>