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

From: Rob Sargent <robjsargent(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: table lock when where clause uses unique constraing instead of primary key.
Date: 2013-11-04 18:51:38
Message-ID: 5277ECBA.30101@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 11/04/2013 11:38 AM, Jeff Amiel wrote:
>
> to: Rob Sargent
>
> The login references have nothing to do with postgres - is simply table/column names being used.
>
>
>
I'm sorry, I thought user_profile.login_attempts was being set to zero
during login (or perhaps after successfulloginin a two-step process) and
that interaction was leading to the "lock storm". Suspected something in
the details therewould be interesting.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jason Long 2013-11-04 19:44:11 ON DELETE CASCADE Question
Previous Message Martijn van Oosterhout 2013-11-04 18:42:14 Re: Suitable Index for my Table