Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-docs-owner+M8323=pgsql+2Ddocs=arkaria.postgresql.org@postgresql.org>)
 id 1ZMePd-0005Rk-Bb
 for pgsql-docs@arkaria.postgresql.org; Tue, 04 Aug 2015 15:45:57 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.84) (envelope-from
 <pgsql-docs-owner+M8323=pgsql+2Ddocs=arkaria.postgresql.org@postgresql.org>)
 id 1ZMePc-0005RW-TU
 for pgsql-docs@arkaria.postgresql.org; Tue, 04 Aug 2015 15:45:56 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
 by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
 (Exim 4.84) (envelope-from <dmitigr@gmail.com>) id 1ZMePc-0005Qw-9C
 for pgsql-docs@postgresql.org; Tue, 04 Aug 2015 15:45:56 +0000
Received: from mail-io0-x229.google.com ([2607:f8b0:4001:c06::229])
 by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
 (Exim 4.84) (envelope-from <dmitigr@gmail.com>) id 1ZMePa-0005yK-2h
 for pgsql-docs@postgresql.org; Tue, 04 Aug 2015 15:45:55 +0000
Received: by ioii16 with SMTP id i16so21053212ioi.0
 for <pgsql-docs@postgresql.org>; Tue, 04 Aug 2015 08:45:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=lCeFn+XfPhlQCafzQ00y1SM62rOFoKEf40fsxxsrzqo=;
 b=dPUSr/WZ/E09PU91OFLMY7DGGCG6Fbk0OIgdYyROx3pXxQdmLdIyIpIVQzjfg/BkTV
 VxhUdY5xQ546vPNGgV/7pL+bRcPeGLO8c0A9wQQ5PJlt6DsZpGK/kBYhi3Zd6Ykj+qVw
 MIzQ2lFOkMs5D8fjcwWBUnXl/AvSoXAYF+B8w+Igx7mUP6v+lOdxgxvvnV3pS0/3CIjK
 yxcy5aXQgbUGPulAZBc+c99i219Ho4CTy9YfsJ3vWILLzTUav3qIeshWnfjy/RNU6KAv
 73JX/4DBdPv1KNiiogYPQTVd0ohsVwqqHsie1GHHLvnZdu6PYtLVRuptflRWeBqibEKT
 aqsg==
MIME-Version: 1.0
X-Received: by 10.107.136.89 with SMTP id k86mr4120729iod.53.1438703153184;
 Tue, 04 Aug 2015 08:45:53 -0700 (PDT)
Received: by 10.79.7.87 with HTTP; Tue, 4 Aug 2015 08:45:53 -0700 (PDT)
Date: Tue, 4 Aug 2015 18:45:53 +0300
Message-ID: 
 <CAAfz9KP1K6KGJ=zmtwp58wsACgCXCnicf_eByF=ocjEQ2YrKtw@mail.gmail.com>
Subject: 25.1. Comparison of Different Solutions
From: Dmitry Igrishin <dmitigr@gmail.com>
To: pgsql-docs <pgsql-docs@postgresql.org>
Content-Type: multipart/alternative; boundary=001a1145a07262070b051c7e2e9b
X-Pg-Spam-Score: -2.0 (--)
List-Archive: <http://archives.postgresql.org/pgsql-docs>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-docs.postgresql.org>
List-Owner: <mailto:pgsql-docs-owner@postgresql.org>
List-Post: <mailto:pgsql-docs@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-docs>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>
X-Mailing-List: pgsql-docs
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

--001a1145a07262070b051c7e2e9b
Content-Type: text/plain; charset=UTF-8

In "Statement-Based Replication Middleware", in
"(PREPARE TRANSACTION and COMMIT PREPARED."
missed closing parenthesis.

In "Synchronous Multimaster Replication" mentioned that
"PostgreSQL does not offer this type of replication, though
PostgreSQL two-phase commit (PREPARE TRANSACTION
and COMMIT PREPARED) can be used to implement this in
application code or middleware."
But in "Notes" of "PREPARE TRANSACTION" menitioned that:
"PREPARE TRANSACTION is not intended for use in applications
or interactive sessions."
I suggest to change to:
"PREPARE TRANSACTION is not intended for typical use in
applications or interactive sessions."

Also in "Notes" of "PREPARE TRANSACTION"
"It is not currently allowed to PREPARE a transaction"
I suggest to change to:
"It is not currently allowed to prepare a transaction".

-- 
// Dmitry.

--001a1145a07262070b051c7e2e9b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>In &quot;Statement-Based Replication Middleware&quot;=
, in<br></div><div>&quot;(PREPARE TRANSACTION and COMMIT PREPARED.&quot;</d=
iv><div>missed=C2=A0closing parenthesis.</div><div><br></div><div>In &quot;=
Synchronous Multimaster Replication&quot; mentioned that</div><div>&quot;Po=
stgreSQL does not offer this type of replication, though</div><div>PostgreS=
QL two-phase commit (PREPARE TRANSACTION</div><div>and COMMIT PREPARED) can=
 be used to implement this in</div><div>application code or middleware.&quo=
t;</div><div>But in &quot;Notes&quot; of=C2=A0&quot;PREPARE TRANSACTION&quo=
t; menitioned that:</div><div>&quot;PREPARE TRANSACTION is not intended for=
 use in applications</div><div>or interactive sessions.&quot;</div><div>I s=
uggest to change to:</div><div>&quot;PREPARE TRANSACTION is not intended fo=
r typical use in</div><div>applications or interactive sessions.&quot;</div=
><div><br></div><div>Also in &quot;Notes&quot; of &quot;PREPARE TRANSACTION=
&quot;</div><div>&quot;It is not currently allowed to PREPARE a transaction=
&quot;</div><div>I suggest to change to:</div><div>&quot;It is not currentl=
y allowed to prepare a transaction&quot;.</div><div><div><div><br></div>-- =
<br><div class=3D"gmail_signature"><div dir=3D"ltr"><div>// Dmitry.<br><br>=
</div></div></div>
</div></div></div>

--001a1145a07262070b051c7e2e9b--