From: | Herouth Maoz <herouth(at)unicell(dot)co(dot)il> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | What's canceling autovacuum tasks? |
Date: | 2011-02-06 15:07:14 |
Message-ID: | B5542D8C-C382-4E24-A6BF-DDD279FDB06E@unicell.co.il |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi there.
During the weekend I've worked for hours on recovering table bloat. Now I was hoping that after the tables are properly trimmed, then after the next delete operation which created dead tuples, autovacuum will go into effect and do its job properly, and prevent the situation from recurring.
Indeed autovacuum started working on some of the tables. At least one of these tables was one that I have trimmed up using CLUSTER. So I was watching that autovacuum process carefully. And then suddenly it was gone, after working for 20-odd hours. And I had even more dead tuples in pg_stat_user_tables for that table than before.
Looking at the log, I get this:
2011-02-06 15:21:42 IST ERROR: canceling autovacuum task
2011-02-06 15:21:42 IST CONTEXT: automatic vacuum of table "reports.alerts.smsq__archive"
Why?
Postgres version is 8.3.11
Thank you,
Herouth
From | Date | Subject | |
---|---|---|---|
Next Message | Radosław Smogura | 2011-02-06 15:20:42 | Re: Feature: vacuum page before write |
Previous Message | Radosław Smogura | 2011-02-06 14:39:08 | Re: PostgreSQL 9.0.3 - collate/ctype order by hu_HU.UTF8 is not correct sorting |