RELEASE SAVEPOINT SQL - Language Statements RELEASE SAVEPOINT destroy a previously defined savepoint RELEASE SAVEPOINT savepoints releasing 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 .) 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. savepoint_name 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 table VALUES (3); SAVEPOINT my_savepoint; INSERT INTO table VALUES (4); RELEASE SAVEPOINT my_savepoint; COMMIT; The above transaction will insert both 3 and 4. The SQL2003 standard specifies that the keyword SAVEPOINT is mandatory. PostgreSQL allows the SAVEPOINT keyword to be omitted. Otherwise, this command is fully conforming.