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 20:39:06
Message-ID: 4B73196A.3030100@idilia.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Alvaro Herrera wrote:
> Jerry Gamache wrote:
>   
>> Yes, I have PID in the logs now. Problem was observed around 13h30,
>> and there was no log output between 13h18 and 13h30.
>> There are messages for table_b (pid 18350) and table_c (pid 18406),
>> but none for table_a.
>>     
>
> Eh, but according to the pg_locks snap you posted, the PID holding the
> table_b lock is (was?) 20490.
>
>   
20490 is the relid of table_b. The PID holding the lock on table_b is 18406.

In response to

pgsql-bugs by date

Next:From: Koichi SuzukiDate: 2010-02-11 14:35:35
Subject: Bug on pg_lesslog
Previous:From: Alvaro HerreraDate: 2010-02-10 20:26:24
Subject: Re: BUG #5321: Parallel restore temporarily deadlocked by autovacuum analyze

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