Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Thu, 14 Oct 2004 00:02:32 -0400
- Message-id: <25217.1097726552@sss.pgh.pa.us> <text/plain>
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
- Follow-Ups:
- Re: SELECT FOR UPDATE and LIMIT 1 behave oddly
- From: Neil Conway
- Re: SELECT FOR UPDATE and LIMIT 1 behave oddly
- From: Josh Berkus
- Re: SELECT FOR UPDATE and LIMIT 1 behave oddly
- References:
- SELECT FOR UPDATE and LIMIT 1 behave oddly
- From: Josh Berkus
- SELECT FOR UPDATE and LIMIT 1 behave oddly
- Prev by Date: SELECT FOR UPDATE and LIMIT 1 behave oddly
- Next by Date: Re: BUG #1273: bad path for english.stop in tsearch2
- Previous by thread: SELECT FOR UPDATE and LIMIT 1 behave oddly
- Next by thread: Re: SELECT FOR UPDATE and LIMIT 1 behave oddly
- Indexes: