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

From Josh Berkus
Subject Re: SELECT FOR UPDATE and LIMIT 1 behave oddly
Date
Msg-id 200410140945.20826.josh@agliodbs.com
Whole thread Raw
In response to Re: SELECT FOR UPDATE and LIMIT 1 behave oddly  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tom,

> The FOR UPDATE part executes after the LIMIT part.  Arguably this is a
> bad thing, but I'm concerned about the compatibility issues if we change
> it.

In that case, maybe I should do a doc patch warning people not to combine
them?

Hmmm .... come to think of it, is there any easy way to query "give me the
first row which is not locked"?    If I tie pg_locks to a query, will I get
wierd effects?  Just musing ....

--
Josh Berkus
Aglio Database Solutions
San Francisco

pgsql-bugs by date:

Previous
From: "Fahad G."
Date:
Subject: 'configure' bug on Mac OS X 10.3.5
Next
From: Neil Conway
Date:
Subject: Re: 'configure' bug on Mac OS X 10.3.5