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

From: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
To: Jeff Amiel <becauseimjeff(at)yahoo(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:25:48
Message-ID: 527802CC.3080503@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 11/04/2013 12:15 PM, Jeff Amiel wrote:
>
>
>
>
>
> 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.
>

Would it be possible to see that audit function?

--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jeff Amiel 2013-11-04 20:44:07 Re: table lock when where clause uses unique constraing instead of primary key.
Previous Message Elliot 2013-11-04 20:24:01 Re: ON DELETE CASCADE Question