From: Tom Lane <tgl@sss.pgh.pa.us>
To: revoohc@gmail.com
Cc: pgsql-admin@postgresql.org
Subject: Re: Question on vacuuming
Date: Tue, 13 Sep 2005 13:46:22 -0400
Message-ID: <25350.1126633582@sss.pgh.pa.us> (raw)
In-Reply-To: <1d219a6f050913084934b5abf@mail.gmail.com>
References: <1d219a6f050913084934b5abf@mail.gmail.com>
Chris Hoover <revoohc@gmail.com> writes:
> there is 1 exception. Everytime there is work to do, it seems to spike our
> load from < 1 to a load of 3+ for a short time. This tends to cause
> significant slowdowns for our customer if they happen to do anything that is
> causing the database to access the drives. It does not seem to matter how
> much work there is to do. Cleaning up 1 page/tuple or 15000 page/tuples
> tends to cause this spike.
No surprise, because vacuum has to read every page of the table to see
if there is anything there to clean up.
> We are running 7.3.4 on Dell 2650 connected to a Dell powervault running
> raid5.
If you were running something a little newer (8.0) you could use the
vacuum_cost_delay knobs to reduce vacuum's impact on I/O 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 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-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, revoohc@gmail.com
Subject: Re: Question on vacuuming
In-Reply-To: <25350.1126633582@sss.pgh.pa.us>
References: <1d219a6f050913084934b5abf@mail.gmail.com> <25350.1126633582@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