Re: BUG #5321: Parallel restore temporarily deadlocked by autovacuum analyze

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Jerry Gamache <jerry(dot)gamache(at)idilia(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5321: Parallel restore temporarily deadlocked by autovacuum analyze
Date: 2010-02-10 15:31:59
Message-ID: 16457.1265815919@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Jerry Gamache wrote:
>> The restore resumed while I was writing this report, and I saw these new
>> entries in the logs:
>>
>> ERROR: canceling autovacuum task
>> CONTEXT: automatic analyze of table "database1.public.table_y"
>> ERROR: canceling autovacuum task
>> CONTEXT: automatic analyze of table "database1.public.table_y"

> This is what I would have expected to happen almost immediately ... what
> are your autovacuum settings? And what's your deadlock timeout?

The other details showed the blockage as being on table_x though.
Was that a typo in obscuring the details, or did the cancel really
happen on an unrelated table?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Wolfgang Fahnenschreiber 2010-02-10 15:42:34 Postgr. 8.2
Previous Message Jerry Gamache 2010-02-10 15:19:43 Re: BUG #5321: Parallel restore temporarily deadlocked by autovacuum analyze