| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Noah Freire <noah(dot)freire(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: autovacuum: I need some explanation |
| Date: | 2008-10-29 18:46:49 |
| Message-ID: | 20081029184649.GF4331@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Noah Freire escribió:
> 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?
That there's no other process doing the same. Did you check
pg_stat_activity to ensure that there's really no autovacuum worker
processing this table?
> <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)
Are these log entries by the same process? Please add %p to
log_line_prefix to see what's going on.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-10-29 18:53:04 | Re: Block-level CRC checks |
| Previous Message | Kevin Grittner | 2008-10-29 18:34:54 | recovery_target_time and last completed transaction log time |