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

[Rob Sargent]

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.