Re: Reducing likelihood of deadlocks (was referential Integrity and SHARE locks) - Mailing list pgsql-hackers

From Marc Munro
Subject Re: Reducing likelihood of deadlocks (was referential Integrity and SHARE locks)
Date
Msg-id 1171384847.6326.34.camel@bloodnok.com
Whole thread Raw
In response to Re: Reducing likelihood of deadlocks (was referential Integrity and SHARE locks)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, 2007-13-02 at 11:38 -0500, Tom Lane wrote:
> Marc Munro <marc@bloodnok.com> writes:
> > From an application developer's standpoint there are few options, none
> > of them ideal:
>
> How about
>
> 4) Make all the FK constraints deferred, so that they are only checked
> at end of transaction.  Then the locking order of transactions that only
> modify C is always C1, C2, ..., P.

Excellent suggestion.  Thank you.

__
Marc

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Reducing likelihood of deadlocks (was referential Integrity and SHARE locks)
Next
From: Gregory Stark
Date:
Subject: Re: Variable length varlena headers redux