Re: pg_autovacuum

From: Sim Zacks <sim(at)compulab(dot)co(dot)il>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Subject: Re: pg_autovacuum
Date: 2005-12-13 08:43:14
Message-ID: 439E89A2.3020008@compulab.co.il
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

This is a sampling of the debug output.

[2005-12-13 09:43:47 IST] DEBUG: 33 All DBs checked in: 278300 usec,
will sleep for 300 secs.
[2005-12-13 09:48:47 IST] DEBUG: 34 All DBs checked in: 171112 usec,
will sleep for 300 secs.
[2005-12-13 09:53:47 IST] DEBUG: updating the database list

Does that mean that it is vacuuming the databases?
One major reason that I think it is not, is that after a while the
system starts getting sluggish and when I run vacuum analyze then it
picks up again.

That leads me to believe that it is not running vacuum analyze.

Thank You
Sim

Jim C. Nasby wrote:
> On Wed, Dec 07, 2005 at 12:11:22PM +0200, Sim Zacks wrote:
>> select version()
>> "PostgreSQL 8.0.1 on i686-pc-linux-gnu, compiled by GCC
>> i686-pc-linux-gnu-gcc (GCC) 3.3.5 (Gentoo Linux 3.3.5-r1, ssp-3.3.2-3,
>> pie-8.7.7.1)"
>>
>> I am using PG_Autovacuum with postgresql 8.01 and it doesn't seem to be
>> doing anything. I've seen it work on other machines where a log item is
>> entered each time a table is touched.
>>
>> I tried starting it with pg_autovacumm -d 1 -U postgres
>> (I purposely didn't daemonize it because I wanted to see what it was
>> doing) and it showed that it was adding all the tables, but then it just
>> sat there for 2 hours without doing anything else.
>>
>> The stats_collector and stats_row_level are both set to true.
>>
>>
>> Neither the postgresql.log file nor the pg_autovacuum.log file have
>> anything about it in them.
>
> Try -d 2; it should give enough info to tell if it's at least checking
> tables.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Benjamin Arai 2005-12-13 08:50:43 Re: Performance large tables.
Previous Message Jim C. Nasby 2005-12-13 08:22:34 Re: Memory Leakage Problem