Re: deadlock in single-row select-for-update + update scenario? How could it happen? - Mailing list pgsql-general

From John R Pierce
Subject Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Date
Msg-id 53F77DEA.7020104@hogranch.com
Whole thread Raw
In response to deadlock in single-row select-for-update + update scenario? How could it happen?  (hubert depesz lubaczewski <depesz@gmail.com>)
Responses Re: deadlock in single-row select-for-update + update scenario? How could it happen?  (hubert depesz lubaczewski <depesz@gmail.com>)
List pgsql-general
On 8/22/2014 9:29 AM, hubert depesz lubaczewski wrote:
> select * from table where pkey = <value> limit 1 for update;

why is there a limit 1 in there?    pkey=somevalue should only return a
single row.   if it DID return multiple rows, you don't have an ORDER
BY, so the limit 1 would be indeterminate.

--
john r pierce                                      37N 122W
somewhere on the middle of the left coast



pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Next
From: Daniele Varrazzo
Date:
Subject: Constraint exclusion on tables partitioned over range types