Forcing WAL flush - Mailing list pgsql-performance

From james
Subject Forcing WAL flush
Date
Msg-id 50EB42F6.6080108@mansionfamily.plus.com
Whole thread Raw
Responses Re: Forcing WAL flush
Re: Forcing WAL flush
List pgsql-performance
Is there a way to force a WAL flush so that async commits (from other
connections) are flushed, short of actually updating a sacrificial row?

Would be nice to do it without generating anything extra, even if it is
something that causes IO in the checkpoint.

Am I right to think that an empty transaction won't do it, and nor will
a transaction that is just a NOTIFY?


pgsql-performance by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: Two Necessary Kernel Tweaks for Linux Systems
Next
From: François Beausoleil
Date:
Subject: Re: Forcing WAL flush