Re: BUG #3883: Autovacuum deadlock with truncate? - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #3883: Autovacuum deadlock with truncate?
Date
Msg-id 20080117165307.GJ17828@alvh.no-ip.org
Whole thread Raw
In response to BUG #3883: Autovacuum deadlock with truncate?  ("Steven Flatt" <steven.flatt@gmail.com>)
Responses Re: BUG #3883: Autovacuum deadlock with truncate?
List pgsql-bugs
Steven Flatt escribió:

> This isn't a postgres deadlock per se, but the end result is that two
> postgres backends are stuck, each waiting on a PGSemaphoreLock that the
> other presumably has.  The processes have been stuck for hours.

Can you reproduce this problem at will?

Are the processes still running (sleeping, rather) so that we can try to
examine them more deeply?

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

pgsql-bugs by date:

Previous
From: "Steven Flatt"
Date:
Subject: BUG #3883: Autovacuum deadlock with truncate?
Next
From: Tom Lane
Date:
Subject: Re: BUG #3881: lo_open leaks memory