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

Re: SELECT FOR UPDATE and LIMIT 1 behave oddly

From: Neil Conway <neilc(at)samurai(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: SELECT FOR UPDATE and LIMIT 1 behave oddly
Date: 2004-10-15 05:37:10
Message-ID: 1097818630.29932.224.camel@localhost.localdomain (view raw or flat)
Thread:
Lists: 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



In response to

Responses

pgsql-bugs by date

Next:From: Josh BerkusDate: 2004-10-15 16:09:47
Subject: Re: SELECT FOR UPDATE and LIMIT 1 behave oddly
Previous:From: Tom LaneDate: 2004-10-15 05:30:16
Subject: Re: SELECT FOR UPDATE and LIMIT 1 behave oddly

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