Re: BUG #5321: Parallel restore temporarily deadlocked by autovacuum analyze - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #5321: Parallel restore temporarily deadlocked by autovacuum analyze
Date
Msg-id 20100210202624.GS4922@alvh.no-ip.org
Whole thread Raw
In response to BUG #5321: Parallel restore temporarily deadlocked by autovacuum analyze  ("Jerry Gamache" <jerry.gamache@idilia.com>)
Responses Re: BUG #5321: Parallel restore temporarily deadlocked by autovacuum analyze
List 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

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #5321: Parallel restore temporarily deadlocked by autovacuum analyze
Next
From: "Eric Pailleau"
Date:
Subject: BUG #5322: Time to perform vacuums