| From: | "Thomas F(dot) O'Connell" <tfo(at)sitening(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PgSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: SELECT Generating Row Exclusive Locks? |
| Date: | 2005-12-01 05:55:03 |
| Message-ID: | DB6A6143-1F21-4A45-9F70-DB0322BAED21@sitening.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Nov 30, 2005, at 11:24 PM, Tom Lane wrote:
> "Thomas F. O'Connell" <tfo(at)sitening(dot)com> writes:
>> I guess I'm still somewhat puzzled by the original statement of the
>> question, then. Why does that particular view of locks occasionally
>> tie a SELECT to a granted Row Exclusive lock?
>
> You sure it's not left over from an update command earlier in the
> same transaction?
Pretty sure, unless the query I posted earlier can cause the display
of leftover commands...
--
Thomas F. O'Connell
Database Architecture and Programming
Co-Founder
Sitening, LLC
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-260-0005 (cell)
615-469-5150 (office)
615-469-5151 (fax)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander M. Pravking | 2005-12-01 07:32:59 | default_index_tablespace? |
| Previous Message | Bruno Wolff III | 2005-12-01 05:31:19 | Re: Finding uniques across a big join |