Re: Silent deadlock possible in current sources - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Silent deadlock possible in current sources
Date
Msg-id 116.967692207@sss.pgh.pa.us
Whole thread Raw
In response to RE: Silent deadlock possible in current sources  ("Mikheev, Vadim" <vmikheev@SECTORBASE.COM>)
List pgsql-hackers
"Mikheev, Vadim" <vmikheev@SECTORBASE.COM> writes:
>> Although this specific lockup mode didn't exist in 7.0.*, it does
>> suggest a possible cause of the deadlocks-with-no-deadlock-report
>> behavior that a couple of people have reported with 7.0: maybe there
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> is another logic path that allows a deadlock involving two 
>> buffer locks, or a buffer lock and a normal lock.  I'm on the
>> warpath now ...

> Buffer locks were implemented in 6.5.

Yeah, but we've only heard about silent deadlocks from people running
7.0.  I'm speculating that some "unrelated" 7.0 change is interacting
badly with the buffer lock management.  Haven't gone digging yet, but
I will.
        regards, tom lane


pgsql-hackers by date:

Previous
From: t-ishii@sra.co.jp
Date:
Subject: Re: How to store unicode?
Next
From: "Dominic J. Eidson"
Date:
Subject: More about "CREATE TABLE" from inside a function/trigger...