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.
-- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com