Re: transactoin id wraparound problem

Ihave a 60Gb db on which I issued a vacuumdb -a call as a superuser. It
as been running for about 20 hours. (All client connections have been
disabled as well as jobs that access any table). I see 0% cpu
utilization. The vacuumdb process by itself takes about 10% memory and
postgres uses very little cpu and some io.(10-20%).

Is there a way to tell vacuumdb to use more resources so it can run
faster?

-----Original Message-----
From: Alvaro Herrera [mailto:alvherre(at)commandprompt(dot)com]
Sent: Wednesday, September 06, 2006 7:48 PM
To: Sriram Dandapani
Cc: Scott Marlowe; Tom Lane; pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] transactoin id wraparound problem

Sriram Dandapani wrote:
> Hi
> I have several such databases to issue vacuum on. If I were to vacuum
> each table individually, would the transaction id be updated after
every
> table vacuum.

No, you must issue database-wide vacuums. Single-table vacuums, even if
done to each and every table, do not suffice.

> Wonder if it is because I have several large partitioned tables that I
> drop every day that don't get vacuumed enough.

The best time of the day to do the vacuum would be just after one such
partition was dropped, one would think.

--
Alvaro Herrera
http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support