mirror of
https://github.com/postgres/postgres.git
synced 2026-04-12 20:46:42 -04:00
d129255077
another section if required by the platform (instead of the old way of building them in section "l" and always transforming them to the platform-specific section). This speeds up the installation on common platforms, and it avoids some funny business with the man page tools and build process.
96 lines
2.4 KiB
Text
96 lines
2.4 KiB
Text
<!--
|
|
$PostgreSQL: pgsql/doc/src/sgml/ref/commit_prepared.sgml,v 1.4 2008/11/14 10:22:45 petere Exp $
|
|
PostgreSQL documentation
|
|
-->
|
|
|
|
<refentry id="SQL-COMMIT-PREPARED">
|
|
<refmeta>
|
|
<refentrytitle id="sql-commit-prepared-title">COMMIT PREPARED</refentrytitle>
|
|
<manvolnum>7</manvolnum>
|
|
<refmiscinfo>SQL - Language Statements</refmiscinfo>
|
|
</refmeta>
|
|
|
|
<refnamediv>
|
|
<refname>COMMIT PREPARED</refname>
|
|
<refpurpose>commit a transaction that was earlier prepared for two-phase commit</refpurpose>
|
|
</refnamediv>
|
|
|
|
<indexterm zone="sql-commit-prepared">
|
|
<primary>COMMIT PREPARED</primary>
|
|
</indexterm>
|
|
|
|
<refsynopsisdiv>
|
|
<synopsis>
|
|
COMMIT PREPARED <replaceable class="PARAMETER">transaction_id</replaceable>
|
|
</synopsis>
|
|
</refsynopsisdiv>
|
|
|
|
<refsect1>
|
|
<title>Description</title>
|
|
|
|
<para>
|
|
<command>COMMIT PREPARED</command> commits a transaction that is in
|
|
prepared state.
|
|
</para>
|
|
</refsect1>
|
|
|
|
<refsect1>
|
|
<title>Parameters</title>
|
|
|
|
<variablelist>
|
|
<varlistentry>
|
|
<term><replaceable class="PARAMETER">transaction_id</replaceable></term>
|
|
<listitem>
|
|
<para>
|
|
The transaction identifier of the transaction that is to be
|
|
committed.
|
|
</para>
|
|
</listitem>
|
|
</varlistentry>
|
|
</variablelist>
|
|
</refsect1>
|
|
|
|
<refsect1>
|
|
<title>Notes</title>
|
|
|
|
<para>
|
|
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.
|
|
</para>
|
|
|
|
<para>
|
|
This command cannot be executed inside a transaction block. The prepared
|
|
transaction is committed immediately.
|
|
</para>
|
|
|
|
<para>
|
|
All currently available prepared transactions are listed in the
|
|
<link linkend="view-pg-prepared-xacts"><structname>pg_prepared_xacts</structname></link>
|
|
system view.
|
|
</para>
|
|
</refsect1>
|
|
|
|
<refsect1 id="sql-commit-prepared-examples">
|
|
<title id="sql-commit-prepared-examples-title">Examples</title>
|
|
<para>
|
|
Commit the transaction identified by the transaction
|
|
identifier <literal>foobar</>:
|
|
|
|
<programlisting>
|
|
COMMIT PREPARED 'foobar';
|
|
</programlisting>
|
|
</para>
|
|
|
|
</refsect1>
|
|
|
|
<refsect1>
|
|
<title>See Also</title>
|
|
|
|
<simplelist type="inline">
|
|
<member><xref linkend="sql-prepare-transaction" endterm="sql-prepare-transaction-title"></member>
|
|
<member><xref linkend="sql-rollback-prepared" endterm="sql-rollback-prepared-title"></member>
|
|
</simplelist>
|
|
</refsect1>
|
|
|
|
</refentry>
|