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

Re: BUG #4290: wrong double subselect with aggregate function

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Andreas <postgresql(at)elbrief(dot)de>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4290: wrong double subselect with aggregate function
Date: 2008-07-09 16:42:14
Message-ID: 21460.1215621734@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Andreas wrote:
>> I expected for min_c_id in the second row 3.

> Which it is if you turn enable_indexscan to off ...

I think one of the subplans isn't getting re-evaluated when it should
be, which would be a botch in the extParam/parParam signaling.  Not sure
yet if it's a planner or executor bug, but more likely the former.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2008-07-09 18:52:04
Subject: Re: BUG #4290: wrong double subselect with aggregate function
Previous:From: Alvaro HerreraDate: 2008-07-09 16:06:46
Subject: Re: BUG #4290: wrong double subselect with aggregatefunction

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