Re: High inserts, bulk deletes - autovacuum vs scheduled vacuum

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
Cc: Jeremy Haile <jhaile(at)fastmail(dot)fm>, pgsql-performance(at)postgresql(dot)org
Subject: Re: High inserts, bulk deletes - autovacuum vs scheduled vacuum
Date: 2007-01-11 03:10:34
Message-ID: 20070111031034.GG15378@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Jim C. Nasby wrote:

> > Is the best way to do that usually to lower the scale factors? Is it
> > ever a good approach to lower the scale factor to zero and just set the
> > thresholds to a pure number of rows? (when setting it for a specific
> > table)
>
> The problem is what happens if autovac goes off and starts vacuuming
> some large table? While that's going on your queue table is sitting
> there bloating. If you have a separate cronjob to handle the queue
> table, it'll stay small, especially in 8.2.

You mean "at least in 8.2". In previous releases, you could vacuum
that queue table until you were blue on the face, but it would achieve
nothing because it would consider that the dead tuples were visible to a
running transaction: that running the vacuum on the large table. This
is an annoyance that was fixed in 8.2.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Jim C. Nasby 2007-01-11 03:42:00 Re: High inserts, bulk deletes - autovacuum vs scheduled vacuum
Previous Message Jim C. Nasby 2007-01-11 01:27:09 Re: High inserts, bulk deletes - autovacuum vs scheduled vacuum