Re: Reducing likelihood of deadlocks (was referential Integrity and SHARE locks)

From: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
To: Marc Munro <marc(at)bloodnok(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Reducing likelihood of deadlocks (was referential Integrity and SHARE locks)
Date: 2007-02-11 18:21:30
Message-ID: 20070211182129.GW64372@nasby.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 08, 2007 at 08:47:42AM -0800, Marc Munro wrote:
> One of the causes of deadlocks in Postgres is that its referential
> integrity triggers can take locks in inconsistent orders. Generally a
> child record will be locked before its parent, but not in all cases.

Where would PostgreSQL lock the parent before the child? AFAIK the
behavior should be consistent...
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavan Deolasee 2007-02-11 18:35:56 Re: HOT for PostgreSQL 8.3
Previous Message Hannu Krosing 2007-02-11 18:16:22 Re: HOT for PostgreSQL 8.3