Re: [GENERAL] SELECT and RowExclusiveLock - Mailing list pgsql-general

From Tom Lane
Subject Re: [GENERAL] SELECT and RowExclusiveLock
Date
Msg-id 14064.1491620694@sss.pgh.pa.us
Whole thread Raw
In response to [GENERAL] SELECT and RowExclusiveLock  (Tim Nelson <timnels@gmail.com>)
List pgsql-general
Tim Nelson <timnels@gmail.com> writes:
> New to Postgres and I have never seen this condition.  We are getting test
> applications hanging on SELECT statements with a RowExclusiveLock.  How can
> a SELECT cause a RowExclusiveLock?

>  relname          |  pid  |       mode       | granted
> --------------------------+-------+------------------+---------
>  sales_transaction_detail |   392 | RowExclusiveLock | t
>  sales_transaction_detail | 19077 | RowExclusiveLock | t
>  sales_transaction_header | 32661 | RowExclusiveLock | t
>  sales_transaction_header |   392 | RowExclusiveLock | t
>  sales_transaction_header | 19077 | RowExclusiveLock | t

Hm, all those entries are showing granted = t, implying that they are
not blocked.  I think you are mis-querying pg_locks or mis-interpreting
the results.

            regards, tom lane


pgsql-general by date:

Previous
From: Joe Conway
Date:
Subject: Re: [GENERAL] Unable to connect to Postgresql
Next
From: rob stone
Date:
Subject: Re: [GENERAL] A change in the Debian install