From: Alvaro Herrera <alvherre@commandprompt.com>
To: Sriram Dandapani <sdandapani@counterpane.com>
Cc: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: transactoin id wraparound problem
Date: Thu, 7 Sep 2006 10:02:40 -0400
Message-ID: <20060907140240.GB5892@alvh.no-ip.org> (raw)
In-Reply-To: <6992E470F12A444BB787B5C937B9D4DF05ABC941@ca-mail1.cis.local>
References: <6992E470F12A444BB787B5C937B9D4DF05ABC941@ca-mail1.cis.local>
Sriram Dandapani wrote:
> 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?
Maybe you have the vacuum cost delay parameters set? IIRC you should
drop vacuum_cost_delay to 0 if you want it to run as fast as possible.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
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: alvherre@commandprompt.com, sdandapani@counterpane.com, smarlowe@g2switchworks.com, tgl@sss.pgh.pa.us
Subject: Re: transactoin id wraparound problem
In-Reply-To: <20060907140240.GB5892@alvh.no-ip.org>
References: <6992E470F12A444BB787B5C937B9D4DF05ABC941@ca-mail1.cis.local> <20060907140240.GB5892@alvh.no-ip.org>
* 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