| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Steve Singer <ssinger(at)ca(dot)afilias(dot)info> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: canceling autovacuum task woes |
| Date: | 2012-07-24 18:21:40 |
| Message-ID: | CA+TgmoZJ-nSqJWrQHovv7By58d=MkwVjhz26TsmMUEFpPsBZtw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 24, 2012 at 2:11 PM, Steve Singer <ssinger(at)ca(dot)afilias(dot)info> wrote:
> On 12-07-24 01:48 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.
>
> Could autovacuum be compacting a lot of space at the end of the table. This
> is described
> in the thread
> http://archives.postgresql.org/message-id/4D8DF88E.7080205@Yahoo.com
You (and Andres) may well be right, but I think the way we find out is
to add some better logging.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2012-07-24 18:24:13 | Re: canceling autovacuum task woes |
| Previous Message | Steve Singer | 2012-07-24 18:11:50 | Re: canceling autovacuum task woes |