Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: Reducing likelihood of deadlocks (was referential Integrity and SHARE locks)
Date
Msg-id 1124.1171384714@sss.pgh.pa.us
Whole thread Raw
In response to Re: Reducing likelihood of deadlocks (was referential Integrity and SHARE locks)  (Marc Munro <marc@bloodnok.com>)
Responses Re: Reducing likelihood of deadlocks (was referential Integrity and SHARE locks)  (Marc Munro <marc@bloodnok.com>)
List pgsql-hackers
Tree view 
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.
        regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: XML changes broke assert-enabled vcbuild
Next
From: Marc Munro
Date:
Subject: Re: Reducing likelihood of deadlocks (was referential Integrity and SHARE locks)