rdelaage/postgresql
1
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2024-10-01 00:41:20 +02:00
Code Issues Packages Projects Releases Wiki Activity

More release-notes copy editing, from Neil Conway.

Browse Source
This commit is contained in:
Tom Lane 2003-11-16 03:23:48 +00:00
parent 3e9a86a38d
commit 51eba617b2
1 changed files with 14 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
doc/src/sgml/release.sgml
View File

@ -1,5 +1,5 @@
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.242 2003/11/15 20:01:11 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.243 2003/11/16 03:23:48 tgl Exp $
--> -->
<appendix id="release"> <appendix id="release">
@ -1059,9 +1059,10 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.242 2003/11/15 20:01:11 tg
<para>Allow cursors outside transactions using <literal>WITH HOLD</literal> (Neil)</para> <para>Allow cursors outside transactions using <literal>WITH HOLD</literal> (Neil)</para>
<para> <para>
In previous releases, cursors were removed at the end of the In previous releases, cursors were removed at the end of the
transaction. Using <literal>WITH HOLD</literal>, the current transaction that created them. Cursors can now be created with
release allows cursors to remain readable after the creating the <literal>WITH HOLD</literal> option, which allows them to
transaction. continue to be accessed after the creating transaction has
committed.
</para> </para>
</listitem> </listitem>
@ -1091,16 +1092,18 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.242 2003/11/15 20:01:11 tg
<para>Properly handle <literal>SCROLL</literal> with cursors, or <para>Properly handle <literal>SCROLL</literal> with cursors, or
report an error (Neil)</para> report an error (Neil)</para>
<para> <para>
Certain cursors can not be fetched backwards optimally. By Allowing random access (both forward and backward scrolling) to
specifying <literal>SCROLL</literal>, extra work will be some kinds of queries cannot be done without some additional
performed to guarantee that the cursor can be fetched in reverse work. If <literal>SCROLL</literal> is specified when the cursor
or random order. is created, this additional work will be performed. Furthermore,
if the cursor has been created with <literal>NO SCROLL</literal>,
no random access is allowed.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Implement SQL-compatible option <literal>FIRST</>, Implement SQL-compatible options <literal>FIRST</>,
<literal>LAST</>, <literal>ABSOLUTE <replaceable>n</></>, <literal>LAST</>, <literal>ABSOLUTE <replaceable>n</></>,
<literal>RELATIVE <replaceable>n</></> for <literal>RELATIVE <replaceable>n</></> for
<command>FETCH</command> and <command>MOVE</command> (Tom) <command>FETCH</command> and <command>MOVE</command> (Tom)
@ -1151,7 +1154,8 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.242 2003/11/15 20:01:11 tg
<para>Make <command>TRUNCATE</command> transaction-safe (Rod)</para> <para>Make <command>TRUNCATE</command> transaction-safe (Rod)</para>
<para> <para>
<command>TRUNCATE</command> can now be used inside a <command>TRUNCATE</command> can now be used inside a
transaction, and rolled back if the transaction aborts. transaction. If the transaction aborts, the changes made by the
<command>TRUNCATE</command> are automatically rolled back.
</para> </para>
</listitem> </listitem>