Re: table lock when where clause uses unique constraing instead of primary key. - Mailing list pgsql-general

From Jeff Amiel
Subject Re: table lock when where clause uses unique constraing instead of primary key.
Date
Msg-id 1383596145.26725.YahooMailNeo@web161402.mail.bf1.yahoo.com
Whole thread Raw
In response to Re: table lock when where clause uses unique constraing instead of primary key.  (Adrian Klaver <adrian.klaver@gmail.com>)
Responses Re: table lock when where clause uses unique constraing instead of primary key.
List pgsql-general




On Monday, November 4, 2013 1:48 PM, Adrian Klaver <adrian.klaver@gmail.com> wrote:


>Any triggers on user_profile?
>Any FK relationship in either direction?


I grepped the schema (just to be sure) - no foreign keys on columns or table at all.
I do have an audit trigger on the table for updates - inserts into an audit table when changes are made and it DOES do
aseparate select from user_profile for other reasons - but not "for update" or anything - no explicit locking. 


pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: ON DELETE CASCADE Question
Next
From: Elliot
Date:
Subject: Re: ON DELETE CASCADE Question