summaryrefslogtreecommitdiffstats
path: root/doc/src/sgml/ref/commit_prepared.sgml
blob: 7299f735c95665f75e4c1904dc889e493a334f41 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
<!--
doc/src/sgml/ref/commit_prepared.sgml
PostgreSQL documentation
-->

<refentry id="sql-commit-prepared">
 <indexterm zone="sql-commit-prepared">
  <primary>COMMIT PREPARED</primary>
 </indexterm>

 <refmeta>
  <refentrytitle>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>

 <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>Examples</title>
  <para>
   Commit the transaction identified by the transaction
   identifier <literal>foobar</literal>:

<programlisting>
COMMIT PREPARED 'foobar';
</programlisting></para>

 </refsect1>

 <refsect1>
  <title>Compatibility</title>

  <para>
   <command>COMMIT PREPARED</command> is a
   <productname>PostgreSQL</productname> 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.
  </para>
 </refsect1>

 <refsect1>
  <title>See Also</title>

  <simplelist type="inline">
   <member><xref linkend="sql-prepare-transaction"/></member>
   <member><xref linkend="sql-rollback-prepared"/></member>
  </simplelist>
 </refsect1>

</refentry>