From: ogjunk-pgjedan@yahoo.com
To: pgsql-admin@postgresql.org
Subject: VACUUMing for 30 minutes
Date: Wed, 15 Dec 2004 22:32:35 -0800 (PST)
Message-ID: <20041216063235.55265.qmail@web12705.mail.yahoo.com> (raw)
Hello,
I have a DB with about 30 tables, where 2 tables are significantly
larger than the rest, and contain a bit over 100,000 rows.
Every night I do these 3 things:
VACUUM;
ANALYZE;
pg_dump
I am noticing that the VACUUM part takes nearly 30 minutes, during
which the DB is not very accessible (and a whole lot of load is put on
the machine in general).
Using pgsession.sh script mentioned earlier, I caught this process
taking a long time:
31179 | mydb | otis | FETCH 100 FROM _pg_dump_cursor
Is there anything one can do to minimize the impact of VACUUM?
I am using PG 7.3.4 on a Linux box with a 1.70GHz Celeron, 1GB RAM, and
a 'regular' IDE disk.
Thanks,
Otis
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: ogjunk-pgjedan@yahoo.com
Subject: Re: VACUUMing for 30 minutes
In-Reply-To: <20041216063235.55265.qmail@web12705.mail.yahoo.com>
References: <20041216063235.55265.qmail@web12705.mail.yahoo.com>
* 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