Postgres Pro
Downloads
Home   >   mailing lists

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

From Rob Sargent
Subject Re: table lock when where clause uses unique constraing instead of primary key.
Date
Msg-id 5277ECBA.30101@gmail.com
Whole thread Raw
In response to Re: table lock when where clause uses unique constraing instead of primary key.  (Jeff Amiel <becauseimjeff@yahoo.com>)
List pgsql-general
Tree view
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 successful login in a two-step process) and that interaction was leading to the "lock storm". Suspected something in the details there would be interesting.

pgsql-general by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Suitable Index for my Table
Next
From: Jason Long
Date:
Subject: ON DELETE CASCADE Question