autovacuum problems

From: Steve Crawford <scrawford(at)pinpointresearch(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Subject: autovacuum problems
Date: 2004-08-02 22:56:15
Message-ID: 200408021556.15542.scrawford@pinpointresearch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I've been running pg_autovacuum for a week or so, now and while I like
it I'm having trouble trusting it.

I have several small (~0-50 record) working tables that have high
insert/update/delete activity. When I first set up pg_autovacuum they
were being vacuumed every ~1-4 hours during the day and less often at
night. Most of the time the tuple count was reasonable.

Now these tables haven't been vacuumed for a couple of days although
the activity on them hasn't changed.

What has changed is that pg_autovacuum reports that the tuple count is
(actually, was at last vacuum) over 12,000 where it is actually more
like 16 so the next vacuum won't happen for quite a while. 12,000+ is
an unreasonable tuple count - it would represent several week's
activity happening at once.

This has happened to at least two working tables. I'm currently
running it as:
pg_autovacuum -d 2 >> autovacuum.log 2>&1 &

I have also encountered another oddity. If I run pg_autovacuum with
all defaults then it appears to analyze every table in every database
every pass.

Any ideas? My searches have turned up nothing useful. Version is
7.4.1.

Cheers,
Steve

Responses

Browse pgsql-general by date

  From Date Subject
Next Message webb 2004-08-02 23:09:16 Data version idea (please discuss)
Previous Message Pierre-Frédéric Caillaud 2004-08-02 20:34:31 Re: psql and md5