Search Postgresql Archives

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "pgsql-general@xxxxxxxxxxxxxx" <pgsql-general@xxxxxxxxxxxxxx>
Subject: Re: table lock when where clause uses unique constraing instead of primary key.
From: Jeff Amiel <becauseimjeff@xxxxxxxxx>
Date: Mon, 4 Nov 2013 10:38:27 -0800 (PST)
In-reply-to: <1383584788.93216.YahooMailNeo@web161406.mail.bf1.yahoo.com>
Reply-to: Jeff Amiel <becauseimjeff@xxxxxxxxx>


to: Rob Sargent

The login references have nothing to do with postgres - is simply table/column names being used.



-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: table lock when where clause uses unique constraing instead of primary key.
  - From: Rob Sargent

References:
- table lock when where clause uses unique constraing instead of primary key.
  - From: Jeff Amiel

Prev by Date: Re: json datatype and table bloat?
Next by Date: Re: Suitable Index for my Table
Previous by thread: Re: table lock when where clause uses unique constraing instead of primary key.
Next by thread: Re: table lock when where clause uses unique constraing instead of primary key.
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux