From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Rodrigo Barboza <rodrigombufrj(at)gmail(dot)com> |
Cc: | pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: auto vaccum is dying |
Date: | 2014-10-04 18:12:26 |
Message-ID: | CAMkU=1ydN2qQ=N2TrCK8Dw_syZHhS2Ju-GF1iemETXk8FB_Efg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Sat, Oct 4, 2014 at 10:31 AM, Rodrigo Barboza <rodrigombufrj(at)gmail(dot)com>
wrote:
>
> On Thu, Oct 2, 2014 at 12:34 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
>
>> On Wed, Oct 1, 2014 at 9:43 PM, Rodrigo Barboza <rodrigombufrj(at)gmail(dot)com>
>> wrote:
>>
>>> Hello, I have a table that receives lots of updates and inserts.
>>> Auto vaccum is always being cancelled on that table.
>>>
>>
>> Do you have a scheduled task that clusters or reindexes the table?
>>
>> Newer versions of PostgreSQL will log the conflicting statement that
>> caused the vacuum to cancel.
>>
>>
> I have nothing scheduled, only auto vacuum, but with the default
> parameters.
>
So what is in the log files pertaining to this?
>
>> Also, what full version are you running?
>>
>>
> I am running postgres 9.1.4 with default auto vacuum parameters. I have
> only a scheduled job that runs delete for old tuples. Sometimes it a lot of
> tuples. Beside that, no other tasks.
>
You are missing 10 minor releases worth of bug fixes, some of which are
related to autovacuuming.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Andrey Lizenko | 2014-10-05 18:57:18 | query plan question, nested loop vs hash join |
Previous Message | Rodrigo Barboza | 2014-10-04 17:31:33 | Re: auto vaccum is dying |