ROLLBACK PREPAREDROLLBACK PREPARED7SQL - Language StatementsROLLBACK PREPAREDcancel a transaction that was earlier prepared for two-phase commit
ROLLBACK PREPARED transaction_idDescriptionROLLBACK PREPARED rolls back a transaction that is in
prepared state.
Parameterstransaction_id
The transaction identifier of the transaction that is to be
rolled back.
Notes
To roll back a prepared transaction, you must be either the same user that
executed the transaction originally, or a superuser. But you do not
have to be in the same session that executed the transaction.
This command cannot be executed inside a transaction block. The prepared
transaction is rolled back immediately.
All currently available prepared transactions are listed in the
pg_prepared_xacts
system view.
If more than one Datanode and/or Coordinator are involved in the
transaction, the ROLLBACK PREPARED> command will propagate to
all the nodes involved.
If xc_maintenance_mode GUC parameter is set to ON, ROLLBACK PREPARED will not propagate to other nodes. It just runs locally and report the result to GTM.
Examples
Roll back the transaction identified by the transaction
identifier foobar>:
ROLLBACK PREPARED 'foobar';
CompatibilityROLLBACK PREPARED is a
PostgreSQL extension. It is intended for use by
external transaction management systems, some of which are covered by
standards (such as X/Open XA), but the SQL side of those systems is not
standardized.
See Also