Provided by: postgresql-client-8.3_8.3.8-1_i386
RELEASE SAVEPOINT - destroy a previously defined savepoint
RELEASE [ SAVEPOINT ] savepoint_name
RELEASE SAVEPOINT destroys a savepoint previously defined in the
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 [rollback_to_savepoint(7)].) Destroying a
savepoint when it is no longer needed allows 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
It is not possible to release a savepoint when the transaction is in an
If multiple savepoints have the same name, only the one that was most
recently defined is released.
To establish and later destroy a savepoint:
INSERT INTO table1 VALUES (3);
INSERT INTO table1 VALUES (4);
RELEASE SAVEPOINT my_savepoint;
The above transaction will insert both 3 and 4.
This command conforms to the SQL standard. The standard specifies that
the key word SAVEPOINT is mandatory, but PostgreSQL allows it to be
BEGIN [begin(7)], COMMIT [commit(l)], ROLLBACK [rollback(l)], ROLLBACK
TO SAVEPOINT [rollback_to_savepoint(l)], SAVEPOINT [savepoint(l)]