From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Subject: | Re: canceling autovacuum task woes |
Date: | 2012-07-24 19:35:28 |
Message-ID: | 1343158466-sup-8270@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Excerpts from Alvaro Herrera's message of mar jul 24 15:30:49 -0400 2012:
>
> > On Tuesday, July 24, 2012 07:48:27 PM Robert Haas wrote:
> > > I am running into a lot of customer situations where the customer
> > > reports that "canceling autovacuum task" shows up in the logs, and
> > > it's unclear whether this is happening often enough to matter, and
> > > even more unclear what's causing it.
> > >
> > > Me: So, do you know what table it's getting cancelled on?
> > > Customer: Nope.
> Hm, autovacuum is supposed to set an errcontext callback that would tell
> you the table name it's working on at the time of the cancel. So if
> even that is missing, something strange is going on.
Yep, it says:
ERROR: canceling autovacuum task
CONTEXT: automatic vacuum of table "alvherre.public.foo"
So at least that part seems pilot error more than anything else.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-07-24 19:37:54 | Re: [patch] libpq one-row-at-a-time API |
Previous Message | Alvaro Herrera | 2012-07-24 19:30:49 | Re: canceling autovacuum task woes |