| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Scott Marlowe <scott(dot)marlowe(at)gmail(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:34:22 |
| Message-ID: | 1255505662.15590.7332.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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
...
--
Simon Riggs www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2009-10-14 07:45:33 | Re: vacuumdb in parallel |
| Previous Message | Scott Marlowe | 2009-10-14 01:40:34 | Re: vacuumdb in parallel |