mirror of
https://github.com/postgres/postgres.git
synced 2025-07-30 11:03:19 +03:00
Revert 0f5ca02f53
0f5ca02f53
introduces 3 new keywords. It appears to be too much for relatively
small feature. Given now we past feature freeze, it's already late for
discussion of the new syntax. So, revert.
Discussion: https://postgr.es/m/28209.1586294824%40sss.pgh.pa.us
This commit is contained in:
@ -21,7 +21,7 @@ PostgreSQL documentation
|
||||
|
||||
<refsynopsisdiv>
|
||||
<synopsis>
|
||||
BEGIN [ WORK | TRANSACTION ] [ <replaceable class="parameter">transaction_mode</replaceable> [, ...] ] [ WAIT FOR LSN <replaceable class="parameter">lsn_value</replaceable> [TIMEOUT <replaceable class="parameter">number_of_milliseconds</replaceable> ] ]
|
||||
BEGIN [ WORK | TRANSACTION ] [ <replaceable class="parameter">transaction_mode</replaceable> [, ...] ]
|
||||
|
||||
<phrase>where <replaceable class="parameter">transaction_mode</replaceable> is one of:</phrase>
|
||||
|
||||
@ -63,17 +63,6 @@ BEGIN [ WORK | TRANSACTION ] [ <replaceable class="parameter">transaction_mode</
|
||||
<xref linkend="sql-set-transaction"/>
|
||||
was executed.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The <literal>WAIT FOR</literal> clause allows to wait for the target log
|
||||
sequence number (<acronym>LSN</acronym>) to be replayed on standby before
|
||||
starting the transaction in <productname>PostgreSQL</productname> databases
|
||||
with master-standby asynchronous replication. Wait time can be limited by
|
||||
specifying a timeout, which is measured in milliseconds and must be a positive
|
||||
integer. If <acronym>LSN</acronym> was not reached before timeout, transaction
|
||||
doesn't begin. Waiting can be interrupted by cancelling
|
||||
<literal>BEGIN</literal> command.
|
||||
</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
@ -157,10 +146,6 @@ BEGIN;
|
||||
different purpose in embedded SQL. You are advised to be careful
|
||||
about the transaction semantics when porting database applications.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
There is no <literal>WAIT FOR</literal> clause in the SQL standard.
|
||||
</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
|
@ -21,7 +21,7 @@ PostgreSQL documentation
|
||||
|
||||
<refsynopsisdiv>
|
||||
<synopsis>
|
||||
START TRANSACTION [ <replaceable class="parameter">transaction_mode</replaceable> [, ...] ] [ WAIT FOR LSN <replaceable class="parameter">lsn_value</replaceable> [TIMEOUT <replaceable class="parameter">number_of_milliseconds</replaceable> ] ]
|
||||
START TRANSACTION [ <replaceable class="parameter">transaction_mode</replaceable> [, ...] ]
|
||||
|
||||
<phrase>where <replaceable class="parameter">transaction_mode</replaceable> is one of:</phrase>
|
||||
|
||||
@ -40,17 +40,6 @@ START TRANSACTION [ <replaceable class="parameter">transaction_mode</replaceable
|
||||
characteristics, as if <xref linkend="sql-set-transaction"/> was executed. This is the same
|
||||
as the <xref linkend="sql-begin"/> command.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The <literal>WAIT FOR</literal> clause allows to wait for the target log
|
||||
sequence number (<acronym>LSN</acronym>) to be replayed on standby before
|
||||
starting the transaction in <productname>PostgreSQL</productname> databases
|
||||
with master-standby asynchronous replication. Wait time can be limited by
|
||||
specifying a timeout, which is measured in milliseconds and must be a positive
|
||||
integer. If <acronym>LSN</acronym> was not reached before timeout, transaction
|
||||
doesn't begin. Waiting can be interrupted by cancelling
|
||||
<literal>START TRANSACTION</literal> command.
|
||||
</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
@ -89,10 +78,6 @@ START TRANSACTION [ <replaceable class="parameter">transaction_mode</replaceable
|
||||
omitted.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
There is no <literal>WAIT FOR</literal> clause in the SQL standard.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
See also the compatibility section of <xref linkend="sql-set-transaction"/>.
|
||||
</para>
|
||||
|
Reference in New Issue
Block a user