| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Herouth Maoz <herouth(at)unicell(dot)co(dot)il> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: What's canceling autovacuum tasks? |
| Date: | 2011-02-06 16:16:15 |
| Message-ID: | 7073.1297008975@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Herouth Maoz <herouth(at)unicell(dot)co(dot)il> writes:
> 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?
Most likely, some other session requested an exclusive lock on the
table. Autovacuum will quit to avoid blocking the other query.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Fitzpatrick | 2011-02-06 17:08:36 | plperl.dll on windows with postgresql 9.0 |
| Previous Message | ray joseph | 2011-02-06 16:14:28 | Re: Looking for Suggestion on Learning |