From: | JanWieck(at)t-online(dot)de (Jan Wieck) |
---|---|
To: | frank <f(dot)callaghan(at)ieee(dot)org> |
Cc: | Fabrice Scemama <fabrices(at)ximmo(dot)ftd(dot)fr>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: [GENERAL] Is Pg 7.0.x's Locking Mechanism BROKEN? |
Date: | 2000-07-26 19:51:34 |
Message-ID: | 200007261951.VAA25141@hot.jw.home |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
frank wrote:
> Thanks Fabrice, that will help a lot.
>
> In my applications the conflict was not a direct table conflict e.g.
> USER1 locks Table1 record that references Table2 via foreign key with a
> cascade update/delete enforced then
> USER2 tried to lock Table2 for update on the referenced record - result both
> users locked !
>
> Is this the same scenario in your case ?
> perhaps a simple test db could used to resolve if this is the issue !
Looks like a deadlock situation not seen by the deadlock
detection code. Unfortunately I'm not able to reproduce a
lockup with a simple test DB. Could you post a simple
(trans1 does ..., trans2 does ...) sample so we coule
reproduce such a lockup?
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
From | Date | Subject | |
---|---|---|---|
Next Message | Timothy H. Keitt | 2000-07-26 19:57:33 | adding column constraint |
Previous Message | Ulf Mehlig | 2000-07-26 19:46:31 | "alter table rename" does not update constraints |
From | Date | Subject | |
---|---|---|---|
Next Message | Henry B. Hotz | 2000-07-26 21:20:11 | Re: Installation Report for powerpc-apple-netbsdelf1.5 |
Previous Message | Jan Wieck | 2000-07-26 19:17:15 | Re: Some questions on user defined types and functions. |