Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
51eba617
Commit
51eba617
authored
Nov 16, 2003
by
Tom Lane
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
More release-notes copy editing, from Neil Conway.
parent
3e9a86a3
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
14 additions
and
10 deletions
+14
-10
doc/src/sgml/release.sgml
doc/src/sgml/release.sgml
+14
-10
No files found.
doc/src/sgml/release.sgml
View file @
51eba617
<!--
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.24
2 2003/11/15 20:01:11
tgl Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.24
3 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
...
@@ -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
...
@@ -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 option
s
<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
...
@@ -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>
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment