mirror of
https://github.com/postgres/postgres.git
synced 2025-07-05 07:21:24 +03:00
6ef2448796
There is what may actually be a mistake in our markup. The problem is in a situation like <para> <command>FOO</command> is ... there is strictly speaking a line break before "FOO". In the HTML output, this does not appear to be a problem, but in the man page output, this shows up, so you get double blank lines at odd places. So far, we have attempted to work around this with an XSL hack, but that causes other problems, such as creating run-ins in places like <acronym>SQL</acronym> <command>COPY</command> So fix the problem properly by removing the extra whitespace. I only fixed the problems that affect the man page output, not all the places.
97 lines
1.9 KiB
Plaintext
97 lines
1.9 KiB
Plaintext
<!--
|
|
doc/src/sgml/ref/rollback.sgml
|
|
PostgreSQL documentation
|
|
-->
|
|
|
|
<refentry id="SQL-ROLLBACK">
|
|
<refmeta>
|
|
<refentrytitle>ROLLBACK</refentrytitle>
|
|
<manvolnum>7</manvolnum>
|
|
<refmiscinfo>SQL - Language Statements</refmiscinfo>
|
|
</refmeta>
|
|
|
|
<refnamediv>
|
|
<refname>ROLLBACK</refname>
|
|
<refpurpose>abort the current transaction</refpurpose>
|
|
</refnamediv>
|
|
|
|
<indexterm zone="sql-rollback">
|
|
<primary>ROLLBACK</primary>
|
|
</indexterm>
|
|
|
|
<refsynopsisdiv>
|
|
<synopsis>
|
|
ROLLBACK [ WORK | TRANSACTION ]
|
|
</synopsis>
|
|
</refsynopsisdiv>
|
|
|
|
<refsect1>
|
|
<title>Description</title>
|
|
|
|
<para>
|
|
<command>ROLLBACK</command> rolls back the current transaction and causes
|
|
all the updates made by the transaction to be discarded.
|
|
</para>
|
|
</refsect1>
|
|
|
|
<refsect1>
|
|
<title>Parameters</title>
|
|
|
|
<variablelist>
|
|
<varlistentry>
|
|
<term><literal>WORK</literal></term>
|
|
<term><literal>TRANSACTION</literal></term>
|
|
<listitem>
|
|
<para>
|
|
Optional key words. They have no effect.
|
|
</para>
|
|
</listitem>
|
|
</varlistentry>
|
|
</variablelist>
|
|
</refsect1>
|
|
|
|
<refsect1>
|
|
<title>Notes</title>
|
|
|
|
<para>
|
|
Use <xref linkend="SQL-COMMIT"> to
|
|
successfully terminate a transaction.
|
|
</para>
|
|
|
|
<para>
|
|
Issuing <command>ROLLBACK</> when not inside a transaction does
|
|
no harm, but it will provoke a warning message.
|
|
</para>
|
|
</refsect1>
|
|
|
|
<refsect1>
|
|
<title>Examples</title>
|
|
|
|
<para>
|
|
To abort all changes:
|
|
<programlisting>
|
|
ROLLBACK;
|
|
</programlisting></para>
|
|
</refsect1>
|
|
|
|
<refsect1>
|
|
<title>Compatibility</title>
|
|
|
|
<para>
|
|
The SQL standard only specifies the two forms
|
|
<literal>ROLLBACK</literal> and <literal>ROLLBACK
|
|
WORK</literal>. Otherwise, this command is fully conforming.
|
|
</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-to"></member>
|
|
</simplelist>
|
|
</refsect1>
|
|
</refentry>
|