On 2016-06-03 20:41:33 -0400, Noah Misch wrote:
> Disabling just backend_flush_after by default works for me, so let's do that.
> Though I would not elect, on behalf of PostgreSQL, the risk of enabling
> {bgwriter,checkpoint,wal_writer}_flush_after by default, a reasonable person
> may choose to do so. I doubt the community could acquire the data necessary
> to ascertain which choice has more utility.
Note that wal_writer_flush_after was essentially already enabled before,
just a lot more *aggressively*.
