| From: | Tim Nelson <timnels(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | SELECT and RowExclusiveLock |
| Date: | 2017-04-07 20:25:02 |
| Message-ID: | CAK09zor4KAGRQaA0E5etdRc+qVoGZk20E5+sJrcQZPLU3RB8Ww@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
pid | age | usename |
query
-------+------------------+----------+----------------------------------------------------------------------------------
32661 | -07:42:39.289945 | postgres | UPDATE "sales_transaction_header"
SET "create_datetime" = '2017-04-07T02:20:39.4
19077 | -07:42:15.976288 | postgres | SELECT "price_benefit"."id",
"price_benefit"."create_datetime", "price_benefit".
392 | -07:01:44.121346 | postgres | SELECT "price_benefit"."id",
"price_benefit"."create_datetime", "price_benefit".
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2017-04-07 20:40:01 | Re: SELECT and RowExclusiveLock |
| Previous Message | Thorsten Glaser | 2017-04-07 18:10:13 | Re: pg_dump: creates dumps that cannot be restored |