From 6eb9c5a5657d1fe77b55cc261450f3538d35a94d Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:19:15 +0200 Subject: Adding upstream version 13.4. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/sql-commit-prepared.html | 33 ++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) create mode 100644 doc/src/sgml/html/sql-commit-prepared.html (limited to 'doc/src/sgml/html/sql-commit-prepared.html') diff --git a/doc/src/sgml/html/sql-commit-prepared.html b/doc/src/sgml/html/sql-commit-prepared.html new file mode 100644 index 0000000..8d17a34 --- /dev/null +++ b/doc/src/sgml/html/sql-commit-prepared.html @@ -0,0 +1,33 @@ + +COMMIT PREPARED
COMMIT PREPARED
Prev UpSQL CommandsHome Next

COMMIT PREPARED

COMMIT PREPARED — commit a transaction that was earlier prepared for two-phase commit

Synopsis

+COMMIT PREPARED transaction_id
+

Description

+ COMMIT PREPARED commits a transaction that is in + prepared state. +

Parameters

transaction_id

+ The transaction identifier of the transaction that is to be + committed. +

Notes

+ To commit 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 committed immediately. +

+ All currently available prepared transactions are listed in the + pg_prepared_xacts + system view. +

Examples

+ Commit the transaction identified by the transaction + identifier foobar: + +

+COMMIT PREPARED 'foobar';
+

Compatibility

+ COMMIT 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. +

Prev Up Next
COMMIT Home COPY
\ No newline at end of file -- cgit v1.2.3