From: Bruce Momjian <pgman@candle.pha.pa.us>
To: jao@geophile.com
Cc: pgsql-performance@postgresql.org
Subject: Re: Configuring PostgreSQL to minimize impact of checkpoints
Date: Mon, 10 May 2004 15:09:32 -0400 (EDT)
Message-ID: <200405101909.i4AJ9Wv09415@candle.pha.pa.us> (raw)
In-Reply-To: <1084215129.409fcf597e163@geophile.com>
jao@geophile.com wrote:
> 4. I understand that a "background writer" is being contemplated for
> 7.5. Will that replace or augment the checkpoint process? Any
> comments on how that work will apply to my problem would be
> appreciated. I wouldn't mind seeing the average performance,
> (without the spikes) go up -- let's say -- 10%, in exchange for
> more uniform performance. These spikes are a real problem.
The background writer is designed to address your specific problem. We
will stil checkpoint, but the spike should be greatly minimized.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
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: pgman@candle.pha.pa.us, jao@geophile.com
Subject: Re: Configuring PostgreSQL to minimize impact of checkpoints
In-Reply-To: <200405101909.i4AJ9Wv09415@candle.pha.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