Re: SELECT FOR UPDATE and LIMIT 1 behave oddly - Mailing list pgsql-bugs

From Neil Conway
Subject Re: SELECT FOR UPDATE and LIMIT 1 behave oddly
Date
Msg-id 1097818630.29932.224.camel@localhost.localdomain
Whole thread Raw
In response to Re: SELECT FOR UPDATE and LIMIT 1 behave oddly  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: SELECT FOR UPDATE and LIMIT 1 behave oddly  (Josh Berkus <josh@agliodbs.com>)
List pgsql-bugs
On Fri, 2004-10-15 at 15:30, Tom Lane wrote:
> Au contraire: every row that gets locked will be returned to the client.
> The gripe at hand is that the number of such rows may be smaller than
> the client wished, because the LIMIT step is applied before we do the
> FOR UPDATE step

Ah, my apologies -- I misunderstood. Clearly not enough coffee this
morning :-)

Sorry for the noise.

-Neil

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: SELECT FOR UPDATE and LIMIT 1 behave oddly
Next
From: Josh Berkus
Date:
Subject: Re: SELECT FOR UPDATE and LIMIT 1 behave oddly