Re: table lock when where clause uses unique constraing instead of primary key.

From: Jeff Amiel <becauseimjeff(at)yahoo(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: table lock when where clause uses unique constraing instead of primary key.
Date: 2013-11-04 20:15:45
Message-ID: 1383596145.26725.YahooMailNeo@web161402.mail.bf1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Monday, November 4, 2013 1:48 PM, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)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 a separate select from user_profile for other reasons - but not "for update" or anything - no explicit locking.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Elliot 2013-11-04 20:24:01 Re: ON DELETE CASCADE Question
Previous Message Adrian Klaver 2013-11-04 20:01:58 Re: ON DELETE CASCADE Question