Message-ID: <542CF64F.6000905@vmware.com>
Date: Thu, 2 Oct 2014 09:53:03 +0300
From: Heikki Linnakangas <hlinnakangas@vmware.com>
Organization: VMware
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Icedove/31.0
MIME-Version: 1.0
To: Rodrigo Barboza <rodrigombufrj@gmail.com>, pgsql-performance
 <pgsql-performance@postgresql.org>
Subject: Re: auto vaccum is dying
References: 
 <CANs8QJY8gc_A8gSF_nbUgd5Qeg+ARtiYKdB-Pkmay6JUzdmFTQ@mail.gmail.com>
In-Reply-To: 
 <CANs8QJY8gc_A8gSF_nbUgd5Qeg+ARtiYKdB-Pkmay6JUzdmFTQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

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@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance