Forcing WAL flush

From: james <james(at)mansionfamily(dot)plus(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Forcing WAL flush
Date: 2013-01-07 21:49:42
Message-ID: 50EB42F6.6080108@mansionfamily.plus.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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?

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message François Beausoleil 2013-01-07 21:55:39 Re: Forcing WAL flush
Previous Message Merlin Moncure 2013-01-07 19:22:13 Re: Two Necessary Kernel Tweaks for Linux Systems