Re: BUG #3883: Autovacuum deadlock with truncate?

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Steven Flatt <steven(dot)flatt(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3883: Autovacuum deadlock with truncate?
Date: 2008-01-17 16:53:07
Message-ID: 20080117165307.GJ17828@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2008-01-17 16:54:02 Re: BUG #3881: lo_open leaks memory
Previous Message Steven Flatt 2008-01-17 16:37:35 BUG #3883: Autovacuum deadlock with truncate?