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

From Mikheev, Vadim
Subject RE: Silent deadlock possible in current sources
Date
Msg-id 8F4C99C66D04D4118F580090272A7A23018CA8@SECTORBASE1
Whole thread Raw
In response to Silent deadlock possible in current sources  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Silent deadlock possible in current sources  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> I'm inclined to think that that is the correct solution and the new
> approach is simply broken.  But, not knowing what Vadim had in mind
> while making this change, I'm going to leave it to him to fix this.

Thanks, Tom! I'll take care about this...

> 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.

Vadim


pgsql-hackers by date:

Previous
From: Mario Weilguni
Date:
Subject: Patch for TNS services
Next
From: Tom Lane
Date:
Subject: Re: How to use the "setof" of CREATE FUNCTION