Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: SELECT FOR UPDATE and LIMIT 1 behave oddly
Date
Msg-id 25217.1097726552@sss.pgh.pa.us
Whole thread Raw
In response to SELECT FOR UPDATE and LIMIT 1 behave oddly  (Josh Berkus <josh@agliodbs.com>)
Responses Re: SELECT FOR UPDATE and LIMIT 1 behave oddly  (Josh Berkus <josh@agliodbs.com>)
Re: SELECT FOR UPDATE and LIMIT 1 behave oddly  (Neil Conway <neilc@samurai.com>)
List pgsql-bugs
Tree view 
Josh Berkus <josh@agliodbs.com> writes:
> Summary:  SELECT FOR UPDATE and LIMIT behave oddly when combined

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.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Josh Berkus
Date:
Subject: SELECT FOR UPDATE and LIMIT 1 behave oddly
Next
From: "Magnus Hagander"
Date:
Subject: Re: BUG #1273: bad path for english.stop in tsearch2