From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
---|---|
To: | Adam Kavan <akavan(at)cox(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_autovacuum |
Date: | 2003-09-03 00:31:51 |
Message-ID: | 1062549111.28884.30.camel@zeutrh9 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 2003-09-02 at 18:30, Adam Kavan wrote:
> Ok I ran pg_autovacuum using the supplied command line and have attached
> the resulting log. My script is just INSERT INTO "PointUsage"
> VALUES(DEFAULT,32,now(),1024); repeated several thousand times. I ran
> autovac, then my script, then verified all of the rows were inserted then
> ran DELETE FROM "PointUsage" WHERE "Value" = 1024; to kill all of the new
> rows, and then killed autovac. The results are attached.
First, I meant to ask for debug level 3, (-d3, not -d2) sorry.... Also,
are you sure that pg_autovacuum is connecting to the same database
cluster as your insert delete script?
In the output you should see the cur_analyze_count increase with each
insert and the curr_delete_count increase with every delete. Also, the
debug output should tell you the threshold you have to reach for a
vacuum or analyze.
From | Date | Subject | |
---|---|---|---|
Next Message | Adam Kavan | 2003-09-03 00:40:17 | Re: pg_autovacuum |
Previous Message | Nigel J. Andrews | 2003-09-03 00:29:08 | Re: Querying $libdir |