| From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
|---|---|
| To: | Noah Freire <noah(dot)freire(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: autovacuum |
| Date: | 2008-10-29 19:46:30 |
| Message-ID: | 4908BD96.8090207@zeut.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Noah Freire wrote:
> <2008-10-29 11:09:03.453 PDT>DEBUG: 00000: accounts: vac: 16697969
> (threshold 6000050), anl: 16697969 (threshold 120000048)
> <2008-10-29 11:09:05.610 PDT>DEBUG: 00000: accounts: vac: 16699578
> (threshold 6000050), anl: 16699578 (threshold 120000048)
> <2008-10-29 11:10:03.563 PDT>DEBUG: 00000: accounts: vac: 16735906
> (threshold 6000050), anl: 16735906 (threshold 120000048)
>
> please check the first log message: the vacuum threshold is 6,000,050
> rows and the number of dead tuples is 16,697,969. Even though the number
> of dead_tuples is greater than the threshold the autovacuum is not being
> triggered for this table. So, besides this condition (dead_tuples >
> threshold) what else is taken into account by autovacuum?
What version of PostgreSQL? Is the table being excluded? (see the
pg_autovacuum system table settings) Are you sure that it's not getting
processed? Perhaps one worker is / has been churning on this table for a
*LONG* time (that is a fairly big table). What does it say for the
most recent autovacuum?
SELECT relid, schemaname, relname, last_vacuum, last_autovacuum from
pg_stat_all_tables;
| From | Date | Subject | |
|---|---|---|---|
| Next Message | x asasaxax | 2008-10-29 20:11:50 | Problem with selecting the first day of the the week |
| Previous Message | Thom Brown | 2008-10-29 18:57:33 | Re: Can't restart Postgres |