Re: pg_autovacuum - Mailing list pgsql-general

From Jim C. Nasby
Subject Re: pg_autovacuum
Date
Msg-id 20051213203727.GW20728@pervasive.com
Whole thread Raw
In response to Re: pg_autovacuum  (Sim Zacks <sim@compulab.co.il>)
List pgsql-general
On Tue, Dec 13, 2005 at 01:24:36PM +0200, Sim Zacks wrote:
> Where can I change the statistic targets?

See the readme for pg_autovacuum. As I mentioned, -V is one of the
parameters you want to track.

> These details for each table are written at the beginning, when I start it.
>
> [2005-12-13 12:38:45 IST] INFO:      table name:
> sales."public"."productdetails"
> [2005-12-13 12:38:45 IST] INFO:         relid: 9451256;   relisshared: 0
> [2005-12-13 12:38:45 IST] INFO:         reltuples: 0.000000;  relpages: 0
> [2005-12-13 12:38:45 IST] INFO:         curr_analyze_count: 0;
> curr_vacuum_count: 0
> [2005-12-13 12:38:45 IST] INFO:         last_analyze_count: 0;
> last_vacuum_count: 0
> [2005-12-13 12:38:45 IST] INFO:         analyze_threshold: 500;
> vacuum_threshold: 1000
> [2005-12-13 12:38:45 IST] DEBUG:   added table:
> sales."public"."productdetails"

I guess it only prints that info out again when it does a vacuum then.
If you look at the statistics for a table where data is changing and
look at the formulas used to decide when to run an analyze or a vacuum,
you can see what tables should be vacuumed soon. In any case, there's
nothing that leads me to believe autovac is broken; I think you just
need to set it to be more aggresive (such as using -V 0.2).
--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

pgsql-general by date:

Previous
From: John Taber
Date:
Subject: php + postgresql pg_connect problem
Next
From: Jaime Casanova
Date:
Subject: Re: triggering on deletes, NEW row or OLD row?