mirror of
https://github.com/postgres/postgres.git
synced 2025-12-19 17:02:53 +03:00
bb4eefe7bf
DocBook XML is superficially compatible with DocBook SGML but has a slightly stricter DTD that we have been violating in a few cases. Although XSLT doesn't care whether the document is valid, the style sheets don't necessarily process invalid documents correctly, so we need to work toward fixing this. This first commit moves the indexterms in refentry elements to an allowed position. It has no impact on the output.
98 lines
2.9 KiB
Plaintext
98 lines
2.9 KiB
Plaintext
<!--
|
|
doc/src/sgml/ref/start_transaction.sgml
|
|
PostgreSQL documentation
|
|
-->
|
|
|
|
<refentry id="SQL-START-TRANSACTION">
|
|
<indexterm zone="sql-start-transaction">
|
|
<primary>START TRANSACTION</primary>
|
|
</indexterm>
|
|
|
|
<refmeta>
|
|
<refentrytitle>START TRANSACTION</refentrytitle>
|
|
<manvolnum>7</manvolnum>
|
|
<refmiscinfo>SQL - Language Statements</refmiscinfo>
|
|
</refmeta>
|
|
|
|
<refnamediv>
|
|
<refname>START TRANSACTION</refname>
|
|
<refpurpose>start a transaction block</refpurpose>
|
|
</refnamediv>
|
|
|
|
<refsynopsisdiv>
|
|
<synopsis>
|
|
START TRANSACTION [ <replaceable class="parameter">transaction_mode</replaceable> [, ...] ]
|
|
|
|
<phrase>where <replaceable class="parameter">transaction_mode</replaceable> is one of:</phrase>
|
|
|
|
ISOLATION LEVEL { SERIALIZABLE | REPEATABLE READ | READ COMMITTED | READ UNCOMMITTED }
|
|
READ WRITE | READ ONLY
|
|
[ NOT ] DEFERRABLE
|
|
</synopsis>
|
|
</refsynopsisdiv>
|
|
|
|
<refsect1>
|
|
<title>Description</title>
|
|
|
|
<para>
|
|
This command begins a new transaction block. If the isolation level,
|
|
read/write mode, or deferrable mode is specified, the new transaction has those
|
|
characteristics, as if <xref linkend="sql-set-transaction"> was executed. This is the same
|
|
as the <xref linkend="sql-begin"> command.
|
|
</para>
|
|
</refsect1>
|
|
|
|
<refsect1>
|
|
<title>Parameters</title>
|
|
|
|
<para>
|
|
Refer to <xref linkend="sql-set-transaction"> for information on the meaning
|
|
of the parameters to this statement.
|
|
</para>
|
|
</refsect1>
|
|
|
|
<refsect1>
|
|
<title>Compatibility</title>
|
|
|
|
<para>
|
|
In the standard, it is not necessary to issue <command>START TRANSACTION</>
|
|
to start a transaction block: any SQL command implicitly begins a block.
|
|
<productname>PostgreSQL</productname>'s behavior can be seen as implicitly
|
|
issuing a <command>COMMIT</command> after each command that does not
|
|
follow <command>START TRANSACTION</> (or <command>BEGIN</command>),
|
|
and it is therefore often called <quote>autocommit</>.
|
|
Other relational database systems might offer an autocommit feature
|
|
as a convenience.
|
|
</para>
|
|
|
|
<para>
|
|
The <literal>DEFERRABLE</literal>
|
|
<replaceable class="parameter">transaction_mode</replaceable>
|
|
is a <productname>PostgreSQL</productname> language extension.
|
|
</para>
|
|
|
|
<para>
|
|
The SQL standard requires commas between successive <replaceable
|
|
class="parameter">transaction_modes</replaceable>, but for historical
|
|
reasons <productname>PostgreSQL</productname> allows the commas to be
|
|
omitted.
|
|
</para>
|
|
|
|
<para>
|
|
See also the compatibility section of <xref linkend="sql-set-transaction">.
|
|
</para>
|
|
</refsect1>
|
|
|
|
<refsect1>
|
|
<title>See Also</title>
|
|
|
|
<simplelist type="inline">
|
|
<member><xref linkend="sql-begin"></member>
|
|
<member><xref linkend="sql-commit"></member>
|
|
<member><xref linkend="sql-rollback"></member>
|
|
<member><xref linkend="sql-savepoint"></member>
|
|
<member><xref linkend="sql-set-transaction"></member>
|
|
</simplelist>
|
|
</refsect1>
|
|
</refentry>
|