From: Richard Huxton <dev@archonet.com>
To: Bastian Voigt <post@bastian-voigt.de>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance Problem with Vacuum of bytea table (PG 8.0.13)
Date: Fri, 25 May 2007 12:51:30 +0100
Message-ID: <4656CDC2.6030106@archonet.com> (raw)
In-Reply-To: <4656C411.8010509@bastian-voigt.de>
References: <46569E6A.2060509@bastian-voigt.de>
<4656BB5E.3000109@archonet.com>
<4656BEF1.4050609@bastian-voigt.de>
<4656C1C7.3000003@archonet.com>
<4656C411.8010509@bastian-voigt.de>
Bastian Voigt wrote:
> Richard Huxton wrote:
>>
>> I was about to say that you can tune pg_autovacuum, but I just checked
>> your original post and you're running 8.0.x - not sure about that one.
> The system catalog pg_autovacuum which allows finetuning autovacuum at
> table level was introduced in 8.1 :-(
Hmm - thought it might have been :-(
>> You'll have to check the documentation for that version to see if you
>> can either:
>> 1. exclude that table from pg_autovacuum
>> 2. increase pg_autovacuum's sensitivity
> (1) seems to be impossible (correct me if I'm wrong..), so maybe I'll go
> for (2) ...
No, the per-table stuff was via the system table.
>> If not, and this table is the most active, it might be simpler just to
>> run your own vacuum-ing from a cron job.
> Well, it is one of the most active, but there are others. pg_autovacuum
> seems to do a very good job, apart from this one table...
Do you have any settings in your postgresql.conf? Failing that, you
would have to poke around the source.
--
Richard Huxton
Archonet Ltd
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: dev@archonet.com, post@bastian-voigt.de
Subject: Re: Performance Problem with Vacuum of bytea table (PG 8.0.13)
In-Reply-To: <4656CDC2.6030106@archonet.com>
* 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