From: | Dorian Hoxha <dorian(dot)hoxha(at)gmail(dot)com> |
---|---|
To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | Rodrigo Barboza <rodrigombufrj(at)gmail(dot)com>, pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: auto vaccum is dying |
Date: | 2014-10-02 07:42:35 |
Message-ID: | CANsFX05fAps-0G17b7C_-qV0e_e6ZXxQmABjHAzg_0NMppf6qg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
I think I've read that when auto-vacuum takes too long, run it more often.
On Thu, Oct 2, 2014 at 8:53 AM, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
wrote:
> On 10/02/2014 07:43 AM, Rodrigo Barboza wrote:
>
>> Hello, I have a table that receives lots of updates and inserts.
>> Auto vaccum is always being cancelled on that table.
>> One day the database went on standby and I had to act manually to recover.
>>
>> What should I do to avoid auto vaccum cancel?
>>
>
> Cancellation happens when you run a command that requires an a stronger on
> the table, like ALTER or TRUNCATE. Plain UPDATEs or INSERTS will not cause
> cancellations. There must be something else going on, causing the
> cancellations.
>
> - Heikki
>
>
>
> --
> Sent via pgsql-performance mailing list (pgsql-performance(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
>
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2014-10-02 08:19:30 | Re: Yet another abort-early plan disaster on 9.3 |
Previous Message | Heikki Linnakangas | 2014-10-02 06:53:03 | Re: auto vaccum is dying |