Re: Concurrent MERGE - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Concurrent MERGE
Date
Msg-id 4C5B3FE1.5030500@agliodbs.com
Whole thread Raw
In response to Re: Concurrent MERGE  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Concurrent MERGE  (Mark Kirkwood <mark.kirkwood@catalyst.net.nz>)
Re: Concurrent MERGE  (Andres Freund <andres@anarazel.de>)
Re: Concurrent MERGE  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> Hm?  Please explain what you're talking about.

Transaction A locks 1 and wants a lock on 2
Transaction B locks 2 and wants a lock on 3
Transaction C locks 3 and wants a lock on 1

I've never had the deadlock detector successfully deal with the above.
Let alone a 4-way.

> Not sure I believe this either; one deadlock kills one transaction.
> If you lose multiple transactions I think you had multiple deadlocks.

Deadlock termination kills *all* of the transactions involved in the
deadlock; what else could it do?  This is as opposed to serialization
failures, in which usually only one of the transactions involved fails.

--                                  -- Josh Berkus                                    PostgreSQL Experts Inc.
                        http://www.pgexperts.com
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Concurrent MERGE
Next
From: Mike Fowler
Date:
Subject: Re: Initial review of xslt with no limits patch