Re: New sync commit mode remote_write - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: New sync commit mode remote_write
Date
Msg-id CA+U5nM+Qz_di6-DN-KV5wD-ZkkGMbPVrd=V+Y6aC0x1bFm5XoA@mail.gmail.com
Whole thread Raw
In response to Re: New sync commit mode remote_write  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: New sync commit mode remote_write  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On Thu, Apr 19, 2012 at 7:50 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> On 4/19/12, Jeff Janes <jeff.janes@gmail.com> wrote:
>> The work around would be for the master to refuse to automatically
>> restart after a crash, insisting on a fail-over instead (or a manual
>> forcing of recovery)?
>
> I suppose that would work, but I think Simon's idea is better: don't
> let the slave replay the WAL until either (a) it's promoted or (b) the
> master finishes the fsync.   That boils down to adding some more
> handshaking to the replication protocol, I think.

It would be 8 bytes on every data message sent to the standby.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Plan stability versus near-exact ties in cost estimates
Next
From: "Albe Laurenz"
Date:
Subject: Re: Plan stability versus near-exact ties in cost estimates