Re: Reporting the commit LSN at commit time - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Reporting the commit LSN at commit time
Date
Msg-id CAB7nPqQRQ7QdTHi2afsVBwzGcnNUkHLXQXsktW+OQYoCYfsMWg@mail.gmail.com
Whole thread Raw
In response to Re: Reporting the commit LSN at commit time  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On Fri, Aug 8, 2014 at 11:58 AM, Fujii Masao <masao.fujii@gmail.com> wrote:
> On Fri, Aug 8, 2014 at 9:50 AM, Craig Ringer <craig@2ndquadrant.com> wrote:
> ISTM that the proper solution to that problem is the introduction of
> new synchronous replication mode which makes the transaction wait for
> its WAL to be replayed by the standby. If this mode is used, a client
> doesn't need to track the LSN of each transaction and check whether
> the committed transaction has already replayed by the standby or not.
Don't you need to combine that with the possibility to wait for N
targets instead of 1 in synchronous_standby_names? You may want to be
sure that the commit is done on a series of standbys before
considering any further operations after this transaction commit.
-- 
Michael



pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Reporting the commit LSN at commit time
Next
From: Tom Lane
Date:
Subject: jsonb format is pessimal for toast compression