From: Alvaro Herrera <alvherre@commandprompt.com>
To: Jim C. Nasby <jim@nasby.net>
Cc: Jeremy Haile <jhaile@fastmail.fm>
Cc: pgsql-performance@postgresql.org
Subject: Re: High inserts, bulk deletes - autovacuum vs scheduled vacuum
Date: Thu, 11 Jan 2007 00:10:34 -0300
Message-ID: <20070111031034.GG15378@alvh.no-ip.org> (raw)
In-Reply-To: <20070111012709.GG12217@nasby.net>
References: <1168363601.5177.1168380907@webmail.messagingengine.com>
<20070110203556.GX12217@nasby.net>
<1168461780.9408.1168619515@webmail.messagingengine.com>
<20070110212125.GZ12217@nasby.net>
<1168465722.17889.1168630713@webmail.messagingengine.com>
<20070111012709.GG12217@nasby.net>
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.
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: alvherre@commandprompt.com, jim@nasby.net, jhaile@fastmail.fm
Subject: Re: High inserts, bulk deletes - autovacuum vs scheduled vacuum
In-Reply-To: <20070111031034.GG15378@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