From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Avoiding deadlocks ... |
Date: | 2010-08-20 08:39:44 |
Message-ID: | 4C6E3F50.80404@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 8/19/10 3:51 PM, Josh Berkus wrote:
> Kevin,
>
> This one is for you:
>
> Two sessions, in transaction:
>
> Process A Process B
>
> update session where id = X;
> update order where orderid = 5;
> update order where orderid = 5;
> update order where orderid = 5;
> ... deadlock error.
Johto on IRC pointed out I left something out of the above: "session" is
referenced in an FK by "orders", and session = X is related to orderid = 5.
>
> It seems like we ought to be able to avoid a deadlock in this case;
> there's a clear precedence of who grabbed the order row first. Does
> your serializability patch address the above situation at all?
>
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2010-08-20 08:50:20 | Re: Avoiding deadlocks ... |
Previous Message | Max Bowsher | 2010-08-20 07:49:09 | Re: git: uh-oh |