Re: vacuumdb in parallel

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Anj Adu <fotographs(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: vacuumdb in parallel
Date: 2009-10-14 07:45:33
Message-ID: dcc563d10910140045r2dfaea1l23da9dbc5956409c@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Wed, Oct 14, 2009 at 1:34 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On Tue, 2009-10-13 at 19:40 -0600, Scott Marlowe wrote:
>> On Tue, Oct 13, 2009 at 7:29 PM, Anj Adu <fotographs(at)gmail(dot)com> wrote:
>> > I am running Postgres 8.1.9 on an 8 core Xeon 5430 box that is showing
>> > single digit CPU and IO utilization. the database size is 820G .
>> > Vacuum_cost_delay=0 and maintenance_mem = 900M
>> >
>> > Is there an option to vacuumdb or a way to make it run parallel threads.
>>
>> I think that option showed up in 8.2 or 8.3.
>
> There is no option to do that yet at any release.
>
> We have parallel pg_restore, but that doesn't apply to vacuumdb,
> reindexdb, clusterdb or any custom written jobs.
>
> You need to break out your top few tables into separate jobs, e.g.
> vacuumdb -t big1
> vacuumdb -t big2

I was thinking of autovacuum, which does indeed have that option.
Much simpler to me, just set the autovac thresholds right and it's
automatic.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Alberto Asuero Arroyo 2009-10-14 08:46:34 how to restore postgre 8.3 from data directory
Previous Message Simon Riggs 2009-10-14 07:34:22 Re: vacuumdb in parallel