On Sat, Apr 21, 2012 at 12:20 AM, Simon Riggs <si...@2ndquadrant.com> wrote: > On Thu, Apr 19, 2012 at 7:50 PM, Robert Haas <robertmh...@gmail.com> wrote: >> On 4/19/12, Jeff Janes <jeff.ja...@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.
There seems to be another problem to solve. In current design of streaming replication, we cannot send any WAL records before writing them locally. Which would mess up the mode which makes a transaction wait for remote write but not local one. We should change walsender so that it can send WAL records before they are written, e.g., send from wal_buffers? Regards, -- Fujii Masao -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
