From: Tom Lane <tgl@sss.pgh.pa.us>
To: ogjunk-pgjedan@yahoo.com
Cc: pgsql-admin@postgresql.org
Subject: Re: VACUUMing for 30 minutes
Date: Wed, 22 Dec 2004 11:14:36 -0500
Message-ID: <4284.1103732076@sss.pgh.pa.us> (raw)
In-Reply-To: <20041222060736.58922.qmail@web12706.mail.yahoo.com>
References: <20041222060736.58922.qmail@web12706.mail.yahoo.com>
<ogjunk-pgjedan@yahoo.com> writes:
> VACUUMing this DB takes about 30 minutes, and during that time the DB
> is pretty unresponsive, although the PG process is not using a lot of
> CPU (load ~ 1) nor memory (~20MB for the VACUUM process).
How big is the DB physically ("du $PGDATA" results)? If you've been lax
about vacuuming or not had your FSM parameters set high enough, there
could be a whole lot of dead space for VACUUM to scan through. If so,
VACUUM FULL or possibly CLUSTER would be the best way to re-compact the
tables. (VACUUM VERBOSE on your larger tables would be another way to
investigate this.)
The other possibility is that you have a seriously slow disk drive :-(
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, ogjunk-pgjedan@yahoo.com
Subject: Re: VACUUMing for 30 minutes
In-Reply-To: <4284.1103732076@sss.pgh.pa.us>
References: <20041222060736.58922.qmail@web12706.mail.yahoo.com> <4284.1103732076@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