From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Gaetano Mendola <mendola@bigfoot.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Determine optimal fdatasync/fsync, O_SYNC/O_DSYNC options
Date: Mon, 13 Sep 2004 22:00:59 -0400
Message-ID: <28518.1095127259@sss.pgh.pa.us> (raw)
In-Reply-To: <200409140128.i8E1S9i04905@candle.pha.pa.us>
References: <200409140128.i8E1S9i04905@candle.pha.pa.us>
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> If we had a majority of queries filling more than one block we would
> be checkpointing like crazy and we don't normally get reports about
> that.
[ raised eyebrow... ] And of course the 30-second-checkpoint-warning
stuff is a useless feature that no one ever exercises.
But your logic doesn't hold up anyway. People may be doing large
transactions without necessarily doing them back-to-back-to-back;
there could be idle time in between. For instance, I'd think an average
transaction size of 100 blocks would be more than enough to make fsync a
winner. There are 2K blocks per WAL segment, so 20 of these would fit
in a segment. With the default WAL parameters you could do sixty such
transactions per five minutes, or one every five seconds, without even
causing more-frequent-than-default checkpoints; and you could do two a
second without setting off the checkpoint-warning alarm. The lack of
checkpoint complaints doesn't prove that this isn't a common real-world
load.
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, pgman@candle.pha.pa.us, mendola@bigfoot.com
Subject: Re: Determine optimal fdatasync/fsync, O_SYNC/O_DSYNC options
In-Reply-To: <28518.1095127259@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