From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jan Wieck <JanWieck@Yahoo.com>
Cc: Jack Orenstein <jao@geophile.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Configuring PostgreSQL to minimize impact of checkpoints
Date: Tue, 11 May 2004 10:41:48 -0400
Message-ID: <9758.1084286508@sss.pgh.pa.us> (raw)
In-Reply-To: <40A0E069.9000006@Yahoo.com>
References: <200405101909.i4AJ9Wv09415@candle.pha.pa.us>
<40A03435.7020300@geophile.com>
<24638.1084245829@sss.pgh.pa.us>
<40A0E069.9000006@Yahoo.com>
Jan Wieck <JanWieck@Yahoo.com> writes:
> If we would combine the background writer and the checkpointer,
... which in fact is on my agenda of things to do ...
> then a
> "checkpoint flush" could actually be implemented as a temporary change
> in that activity that basically is done by not reevaluating the list of
> to be flushed blocks any more and switching to a constant amount of
> blocks flushed per cycle. When that list get's empty, the checkpoint
> flush is done, the checkpoint can complete and the background writer
> resumes normal business.
Sounds like a plan. I'll do it that way. However, we might want to
have different configuration settings controlling the write rate during
checkpoint and the rate during normal background writing --- what do you
think?
Also, presumably a shutdown checkpoint should just whomp out the data
without any delays. We can't afford to wait around and risk having
init decide we took too long.
>> None of this is necessarily going to fix matters for an installation
>> that has no spare I/O capacity, though.
> As a matter of fact, the background writer increases the overall IO. It
> writes buffers that possibly get modified again before a checkpoint or
> their replacement requires them to be finally written. So if there is no
> spare IO bandwidth, it makes things worse.
Right, the trickle writes could be wasted effort.
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, JanWieck@Yahoo.com, jao@geophile.com
Subject: Re: Configuring PostgreSQL to minimize impact of checkpoints
In-Reply-To: <9758.1084286508@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