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

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

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Jerry Gamache <jerry(dot)gamache(at)idilia(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:26:24
Message-ID: 20100210202624.GS4922@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-bugs
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.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

pgsql-bugs by date

Next:From: Jerry GamacheDate: 2010-02-10 20:39:06
Subject: Re: BUG #5321: Parallel restore temporarily deadlocked by autovacuum analyze
Previous:From: Jerry GamacheDate: 2010-02-10 20:23:22
Subject: Re: BUG #5321: Parallel restore temporarily deadlocked by autovacuum analyze

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