On Tue, Feb 28, 2017 at 12:08 PM, Erik Rijkers <e...@xs4all.nl> wrote: > Would you remind me why synchronous_commit = on was deemed a better default?
I'm wondering about that, too. If you're trying to do logical synchronous replication, then maybe there's some argument there, although even in that case I am not sure it's actually necessary. But if you're doing asynchronous logical replication, it seems not to make much sense. I mean, walwriter is going to flush the WAL to disk within a fraction of a second; why would we wait for that to happen instead of getting on with replicating the next transaction meanwhile? (There may well be an aspect to this I'm missing, so please forgive me if the above is off-base.) -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers