From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kevin Brown <kevin@sysexperts.com>
Cc: Hackers <pgsql-hackers@postgresql.org>
Cc: pgsql-performance@postgresql.org, Advocacy <pgsql-advocacy@postgresql.org>
Subject: Re: [PERFORM] [HACKERS] More benchmarking of wal_buffers
Date: Thu, 13 Feb 2003 23:14:49 -0500
Message-ID: <3914.1045196089@sss.pgh.pa.us> (raw)
In-Reply-To: <20030214034646.GA1847@filer>
References: <GNELIHDDFBOCMGBFGEFOKEIKCFAA.chriskl@familyhealth.com.au>
<3331.1045189757@sss.pgh.pa.us>
<20030214034646.GA1847@filer>
Kevin Brown <kevin@sysexperts.com> writes:
> What happens when the only transaction running emits more WAL log data
> than wal_buffers can handle? A flush happens when the WAL buffers
> fill up (that's what I'd expect)? Didn't find much in the
> documentation about it...
A write, not a flush (ie, we don't force an fsync). Also, I think it
writes only a few blocks, not all the available data. Don't recall the
details on that.
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, kevin@sysexperts.com, pgsql-hackers@postgresql.org, pgsql-advocacy@postgresql.org
Subject: Re: [PERFORM] [HACKERS] More benchmarking of wal_buffers
In-Reply-To: <3914.1045196089@sss.pgh.pa.us>
References: <GNELIHDDFBOCMGBFGEFOKEIKCFAA.chriskl@familyhealth.com.au> <3331.1045189757@sss.pgh.pa.us> <20030214034646.GA1847@filer> <3914.1045196089@sss.pgh.pa.us>
* 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