Skip site navigation (1) Skip section navigation (2)

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

From: Jerry Gamache <jerry(dot)gamache(at)idilia(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5321: Parallel restore temporarily deadlocked by autovacuum analyze
Date: 2010-02-10 19:49:34
Message-ID: 4B730DCE.3000809@idilia.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Here is the pg_locks output.

Alvaro Herrera wrote:
> Jerry Gamache wrote:
>   
>> I was not able to repro with default parameters, or at 15s naptime,
>> and at 1s naptime I got only 1deadlock in 3 tests.
>>
>> This time the deadlock was with table_a, table_b and table_c
>> (table_x and table_y were not involved).
>>
>>   18395 | database1 | autovacuum: ANALYZE public.table_a
>>   18406 | database1 | autovacuum: ANALYZE public.table_b
>>   18510 | database1 |
>>                            : CREATE UNIQUE INDEX index_bg ON table_b
>> USING btree (col_g);
>>   18567 | database1 | autovacuum: ANALYZE public.table_c
>>   18802 | database1 | select procpid,datname,current_query from
>> pg_stat_activity where datname='database1' ORDER BY procpid;
>>
>> There is a FK constraint between table_a and table_b, but table_c
>> does not have any direct constraint relation with the other 2
>> tables.
>>
>> The logs show that the autovacuum of table_b was canceled 20 minutes
>> ago, but the thread is still alive and blocked.
>>     
>
> That's pretty strange.  Can we see a pg_locks snapshot?  (Please attach
> as a text file so that it doesn't get word-wrapped)
>
>   


Attachment: pg_842_lock_status.txt
Description: text/plain (4.6 KB)

In response to

Responses

pgsql-bugs by date

Next:From: Alvaro HerreraDate: 2010-02-10 20:02:49
Subject: Re: BUG #5321: Parallel restore temporarily deadlocked by autovacuum analyze
Previous:From: Alvaro HerreraDate: 2010-02-10 19:19:24
Subject: Re: BUG #5321: Parallel restore temporarily deadlocked by autovacuum analyze

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group