From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
Cc: | Postgres general mailing list <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Autovacuum keeps vacuuming a table disabled in pg_autovacuum |
Date: | 2007-06-01 13:58:25 |
Message-ID: | 20070601135825.GC4503@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Csaba Nagy wrote:
> Trouble: the autovacuum daemon is still taking that table and vacuums
> it... how do I know ? So:
>
> select l.pid,c.relname from pg_locks l, pg_class c where l.pid not in
> (select distinct procpid from pg_stat_activity) and l.relation=c.oid and
> c.relkind='r';
>
> pid | relname
> -------+------------
> 16317 | table_name
> (1 row)
>
> postgres(at)dbname:~$ ps auxww|grep auto
> postgres 16317 0.8 5.8 436008 240656 ? D 13:26 0:55 postgres:
> autovacuum process dbname
Probably autovacuum is worried about Xid wraparound so it tries to do a
database-wide vacuum. In these cases it ignores the pg_autovacuum
disable.
Try reindexing the table; that should make the problem go away. Also,
update to the latest of the 8.1 branch ASAP.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Erik Jones | 2007-06-01 14:15:31 | Re: shut down one database? |
Previous Message | Csaba Nagy | 2007-06-01 13:58:06 | Re: Autovacuum keeps vacuuming a table disabled in pg_autovacuum |