From: | "Mason Hale" <masonhale(at)gmail(dot)com> |
---|---|
To: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: vacuum taking an unusually long time |
Date: | 2008-07-15 15:38:15 |
Message-ID: | 8bca3aa10807150838w68884f7bx2942a90f9a741eb6@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
None of these values have changed recently.
The values are:
vacuum_cost_delay = 10ms
vacuum_cost_limit = 200
Are there any other values I should be looking at?
The longest running vacuum has been running more than 6 days at this point.
Thanks,
Mason
On Mon, Jul 14, 2008 at 4:39 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
wrote:
> On Mon, Jul 14, 2008 at 3:08 PM, Mason Hale <masonhale(at)gmail(dot)com> wrote:
> > Vacuum operations on several tables are taking much longer than they
> > previously were.
> > We currently have 3 autovacuum processes that have been running more than
> 3
> > days each.
> > The tables are large (between 40 and 90GB each).
> > Postgresql version is 8.3.1
> > maintenance_work_mem is 512MB (on a 32GB server).
> > Any ideas what would make vacuum take so long?
> > What can I do to speed things up?
>
> Have you adjusted your vacuum / autovacuum cost parameters up? that
> will certainly slow down vacuums.
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2008-07-15 16:06:43 | Re: [pgsql-advocacy] Pg booth staffing at OSCON |
Previous Message | Craig Ringer | 2008-07-15 15:37:52 | Re: C-procedure crashed in Postgres 8.3.3 when using 'text' variable (WinXP) |