Re: Deadlock situation using foreign keys (reproduceable)

From: Thomas O'Dowd <tom(at)nooper(dot)com>
To: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Deadlock situation using foreign keys (reproduceable)
Date: 2002-08-26 04:33:39
Message-ID: 1030336420.4353.112.camel@beast.uwillsee.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thanks for your feedback Stephan. Seems like a tough fix. Pitty it won't
make it into 7.3. I presume there are other folk out there suffering
from the same problems that I'm having. What approaches if any have
people taken to work around this problem? I read in the list that one
user patched his postmaster to explictly ignore the RI "FOR UPDATE" on
tables he knew weren't changing. Can't find the detailed message in the
archives right now, but I read it earlier. Any other work-arounds?

Tom.

On Mon, 2002-08-26 at 12:46, Stephan Szabo wrote:
> > My question is if this is now resolved for 7.3? I'm trying to figure out
> > what I can do with my 7.2.1 problems... Has anyone got a back-ported
> > patch, perhaps against 7.2.2?
>
> It's actually not resolved because my attempts at the lower strength lock
> opened up holes and fixing those opened up new deadlock situations, and
> I ran out of time in the 7.3 cycle to try to make it work.
--
Thomas O'Dowd. - Nooping - http://nooper.com
tom(at)nooper(dot)com - Testing - http://nooper.co.jp/labs

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephan Szabo 2002-08-26 04:58:23 Re: Deadlock situation using foreign keys (reproduceable)
Previous Message Marc G. Fournier 2002-08-26 04:23:54 Re: PostgreSQL 7.2.2 and docs