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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers