Skip site navigation (1) Skip section navigation (2)

VACUUMing for 30 minutes

From: <ogjunk-pgjedan(at)yahoo(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: VACUUMing for 30 minutes
Date: 2004-12-16 06:32:35
Message-ID: 20041216063235.55265.qmail@web12705.mail.yahoo.com (view raw or flat)
Thread:
Lists: pgsql-admin
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


Responses

pgsql-admin by date

Next:From: William YuDate: 2004-12-16 07:14:03
Subject: Re: Tyan Thunder MB for postgres server
Previous:From: IainDate: 2004-12-16 02:18:37
Subject: Re: Tyan Thunder MB for postgres server

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group