From: | Andreas 'ads' Scherbaum <adsmail(at)wars-nicht(dot)de> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Problem with autovacuum and pg_autovacuum |
Date: | 2007-07-04 21:42:53 |
Message-ID: | 20070704234253.7f7c8af4.adsmail@wars-nicht.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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)
Now it seems, that autovacuum is processing exactly this tables:
2007-07-04 22:37:05 CEST DEBUG: autovacuum: processing database "database1"
2007-07-04 22:37:06 CEST DEBUG: autovac: will VACUUM ANALYZE users
2007-07-04 22:37:06 CEST DEBUG: autovac: will VACUUM ANALYZE user_stats
2007-07-04 22:37:06 CEST DEBUG: autovac: will VACUUM ANALYZE guestbook
2007-07-04 22:37:06 CEST DEBUG: autovac: will VACUUM ANALYZE forum_fora
2007-07-04 22:37:06 CEST DEBUG: autovac: will VACUUM ANALYZE forum_threads
2007-07-04 22:37:06 CEST DEBUG: autovac: will VACUUM ANALYZE forum_thread_entries
2007-07-04 22:37:06 CEST DEBUG: autovac: will VACUUM ANALYZE user_data
2007-07-04 22:37:06 CEST DEBUG: autovac: will VACUUM ANALYZE user_online
2007-07-04 22:37:06 CEST DEBUG: vacuuming "schema1.users"
2007-07-04 22:38:39 CEST DEBUG: vacuuming "pg_toast.pg_toast_41570"
2007-07-04 22:38:47 CEST DEBUG: vacuuming "schema1.user_stats"
2007-07-04 22:49:06 CEST DEBUG: vacuuming "pg_toast.pg_toast_43602"
2007-07-04 22:51:51 CEST DEBUG: vacuuming "schema1.guestbook"
2007-07-04 23:00:38 CEST DEBUG: vacuuming "pg_toast.pg_toast_42041"
2007-07-04 23:00:43 CEST DEBUG: vacuuming "schema1.forum_fora"
2007-07-04 23:00:50 CEST DEBUG: vacuuming "pg_toast.pg_toast_42255"
2007-07-04 23:00:50 CEST DEBUG: vacuuming "schema1.forum_threads"
2007-07-04 23:01:06 CEST DEBUG: vacuuming "schema1.forum_thread_entries"
2007-07-04 23:01:50 CEST DEBUG: vacuuming "pg_toast.pg_toast_42406"
2007-07-04 23:01:54 CEST DEBUG: vacuuming "schema1.user_data"
2007-07-04 23:05:36 CEST DEBUG: vacuuming "pg_toast.pg_toast_41694"
2007-07-04 23:05:45 CEST DEBUG: vacuuming "schema1.user_online"
database1=# select version();
version
-----------------------------------------------------------------------------------------------------------------
PostgreSQL 8.2.4 on x86_64-pc-linux-gnu, compiled by GCC cc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)
(1 row)
Any idea, what's wrong here?
Kind regards
--
Andreas 'ads' Scherbaum
Failure is not an option. It comes bundled with your Microsoft product.
(Ferenc Mantfeld)
From | Date | Subject | |
---|---|---|---|
Next Message | wu_zhong_min | 2007-07-04 21:43:57 | perpetual dump/restore problem |
Previous Message | wu_zhong_min | 2007-07-04 21:35:10 | Re: [general] growing disk usage problem: alternative solution? |