mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Make it more clear that you need to release savepoint with

Browse Source 
RELEASE SAVEPOINT to make an older savepoint with the same name
accessible. It's also possible to implicitly release the savepoint by
rolling back to an earlier savepoint, but mentioning that too would make
the note just more verbose and confusing.
This commit is contained in:
Heikki Linnakangas 2010-05-27 06:25:32 +00:00
parent 5e85315ea7
commit aa5bec67de
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/src/sgml/ref/savepoint.sgml
View File

@ -1,5 +1,5 @@
<!--
$PostgreSQL: pgsql/doc/src/sgml/ref/savepoint.sgml,v 1.7 2010/04/03 07:23:02 petere Exp $
$PostgreSQL: pgsql/doc/src/sgml/ref/savepoint.sgml,v 1.8 2010/05/27 06:25:32 heikki Exp $
PostgreSQL documentation
-->
@ -116,9 +116,10 @@ COMMIT;
savepoint with the same name is established. In
<productname>PostgreSQL</>, the old savepoint is kept, though only the more
recent one will be used when rolling back or releasing. (Releasing the
newer savepoint will cause the older one to again become accessible to
<command>ROLLBACK TO SAVEPOINT</> and <command>RELEASE SAVEPOINT</>.)
Otherwise, <command>SAVEPOINT</command> is fully SQL conforming.
newer savepoint with <command>RELEASE SAVEPOINT</> will cause the older one
to again become accessible to <command>ROLLBACK TO SAVEPOINT</> and
<command>RELEASE SAVEPOINT</>.) Otherwise, <command>SAVEPOINT</command> is
fully SQL conforming.
</para>
</refsect1>