Hi, On Thu, Nov 12, 2009 at 4:32 PM, Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> wrote: > Fujii Masao wrote: >> The problem is that fsync needs to be issued too frequently, which would >> be harmless in asynchronous replication, but not in synchronous one. >> A transaction would have to wait for the primary's and standby's fsync >> before returning a "success" to a client. >> >> So I'm inclined to change the startup process and bgwriter, instead of >> walreceiver, so as to fsync the WAL for the WAL rule. > > Let's keep it simple for now. Just make the walreceiver do the fsync. We > can optimize later. For now, we're only going to have async mode anyway.
Okey, I'll do that; the walreceiver issues the fsync for each arrival of the WAL records, and the startup process replays only the records already fsynced. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
