From: Tom Lane <tgl@sss.pgh.pa.us>
To: Christopher Petrilli <petrilli@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Impact of checkpoint_segments under continual load conditions
Date: Sun, 17 Jul 2005 14:15:54 -0400
Message-ID: <18942.1121624154@sss.pgh.pa.us> (raw)
In-Reply-To: <59d991c4050717100874c08a86@mail.gmail.com>
References: <59d991c4050717100874c08a86@mail.gmail.com>
Christopher Petrilli <petrilli@gmail.com> writes:
> I have a unique scenerio. My DB is under "continual load", meaning
> that I am constantly using COPY to insert new data into the DB. There
> is no "quiet period" for the database, at least not for hours on end.
> Normally, checkpoint_segments can help absorb some of that, but my
> experience is that if I crank the number up, it simply delays the
> impact, and when it occurs, it takes a VERY long time (minutes) to
> clear.
If you are using 8.0, you can probably alleviate the problem by making
the bgwriter more aggressive. I don't have any immediate
recommendations for specific settings though.
A small checkpoint_segments setting is definitely bad news for
performance under heavy 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, petrilli@gmail.com
Subject: Re: Impact of checkpoint_segments under continual load conditions
In-Reply-To: <18942.1121624154@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