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

From hubert depesz lubaczewski
Subject Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Date
Msg-id CAKrjmhfQiyzK=UJVWObXdu4ero6KY9CcMSwkWnJ823fsqnyn7w@mail.gmail.com
Whole thread Raw
In response to Re: deadlock in single-row select-for-update + update scenario? How could it happen?  (John R Pierce <pierce@hogranch.com>)
List pgsql-general
On Fri, Aug 22, 2014 at 7:29 PM, John R Pierce <pierce@hogranch.com> wrote:
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.

leftover from some other thing.

depesz

pgsql-general by date:

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