From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | Bastian Voigt <post(at)bastian-voigt(dot)de> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Performance Problem with Vacuum of bytea table (PG 8.0.13) |
Date: | 2007-05-25 11:51:30 |
Message-ID: | 4656CDC2.6030106@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Bastian Voigt | 2007-05-25 12:30:36 | My quick and dirty "solution" (Re: Performance Problem with Vacuum of bytea table (PG 8.0.13)) |
Previous Message | Bastian Voigt | 2007-05-25 11:10:09 | Re: Performance Problem with Vacuum of bytea table (PG 8.0.13) |