From: james <james@mansionfamily.plus.com>
To: François Beausoleil <francois@teksol.info>
Cc: pgsql-performance@postgresql.org
Subject: Re: Forcing WAL flush
Date: Mon, 07 Jan 2013 22:05:38 +0000
Message-ID: <50EB46B2.2080503@mansionfamily.plus.com> (raw)
In-Reply-To: <F92B51B0-FD33-4EA8-8540-D775E3B9F235@teksol.info>
References: <50EB42F6.6080108@mansionfamily.plus.com>
<F92B51B0-FD33-4EA8-8540-D775E3B9F235@teksol.info>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
> Le 2013-01-07 à 16:49, james a écrit :
>
>> 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?
>
> Does pg_start_backup() trigger a full WAL flush?
>
> http://www.postgresql.org/docs/9.2/static/continuous-archiving.html#BACKUP-LOWLEVEL-BASE-BACKUP
> http://www.postgresql.org/docs/9.2/static/functions-admin.html#FUNCTIONS-ADMIN-BACKUP-TABLE
>
> Bye,
> François
That sounds rather heavyweight!
I'm looking for something lightweight - I might call this rather often,
as a sort of application-level group commit where I commit async but
defer the ack to the requester (or other externally visible side
effects) slightly until some other thread forces a flush.
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: james@mansionfamily.plus.com, francois@teksol.info
Subject: Re: Forcing WAL flush
In-Reply-To: <50EB46B2.2080503@mansionfamily.plus.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox