Skip site navigation (1) Skip section navigation (2)

Re: SELECT FOR UPDATE and LIMIT 1 behave oddly

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: josh(at)agliodbs(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: SELECT FOR UPDATE and LIMIT 1 behave oddly
Date: 2004-10-14 04:02:32
Message-ID: 25217.1097726552@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Josh Berkus <josh(at)agliodbs(dot)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

In response to

Responses

pgsql-bugs by date

Next:From: Magnus HaganderDate: 2004-10-14 07:55:33
Subject: Re: BUG #1273: bad path for english.stop in tsearch2
Previous:From: Josh BerkusDate: 2004-10-14 01:05:43
Subject: SELECT FOR UPDATE and LIMIT 1 behave oddly

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group