From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | "Andreas 'ads' Scherbaum" <adsmail(at)wars-nicht(dot)de> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Problem with autovacuum and pg_autovacuum |
Date: | 2007-07-04 22:04:35 |
Message-ID: | 20070704220435.GK5035@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Andreas 'ads' Scherbaum wrote:
>
> Hello,
>
> we got a small problem with auto_vacuum: since we have some big tables
> which have heavy read/write access, we tried to exclude this tables
> from autovacuum:
>
> database1=# select vacrelid,enabled,(select relname from pg_class where oid=vacrelid) as relname from pg_autovacuum;
> vacrelid | enabled | relname
> ----------+---------+----------------------
> 42041 | f | guestbook
> 42344 | f | forum_threads
> 42406 | f | forum_thread_entries
> 41937 | f | user_online
> 42255 | f | forum_fora
> 41570 | f | users
> 41694 | f | user_data
> (7 rows)
Most likely it is worried about XID wraparound, and those are precisely
the tables that need urgent vacuumed because they haven't been vacuumed
in a long time.
What do you do to keep them clear of dead tuples?
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas 'ads' Scherbaum | 2007-07-04 22:17:46 | Re: Problem with autovacuum and pg_autovacuum |
Previous Message | wu_zhong_min | 2007-07-04 21:43:57 | perpetual dump/restore problem |