|PostgreSQL Reference Manual - Volume 1 - SQL Language Reference|
by The PostgreSQL Global Development Group
Paperback (6"x9"), 716 pages
RRP £32.00 ($49.95)
Sales of this book support the PostgreSQL project! Get a printed copy>>>
12.92 RELEASE SAVEPOINT
RELEASE SAVEPOINT -- destroy a previously defined savepoint
RELEASE [ SAVEPOINT ] savepoint_name
RELEASE SAVEPOINT destroys a savepoint previously defined
in the current transaction.
Destroying a savepoint makes it unavailable as a rollback point,
but it has no other user visible behavior. It does not undo the
effects of commands executed after the savepoint was established.
(To do that, see
ROLLBACK TO SAVEPOINT.) Destroying a savepoint when
it is no longer needed may allow the system to reclaim some resources
earlier than transaction end.
RELEASE SAVEPOINT also destroys all savepoints that were
established after the named savepoint was established.
- The name of the savepoint to destroy.
Specifying a savepoint name that was not previously defined is an error.
It is not possible to release a savepoint when the transaction is in an aborted state.
If multiple savepoints have the same name, only the one that was most recently defined is released.
To establish and later destroy a savepoint:
BEGIN; INSERT INTO table1 VALUES (3); SAVEPOINT my_savepoint; INSERT INTO table1 VALUES (4); RELEASE SAVEPOINT my_savepoint; COMMIT;
The above transaction will insert both 3 and 4.
This command conforms to the SQL standard. The standard
specifies that the key word
mandatory, but PostgreSQL allows it to
|ISBN 0954612027||PostgreSQL Reference Manual - Volume 1 - SQL Language Reference||See the print edition|