I wrote:
> 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.
So, stripping the problem query down to its essentials, we have
regressi
Alvaro Herrera <[EMAIL PROTECTED]> 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. N
Andreas wrote:
> min_c_id | b_aid | min_c_id_1 | min_c_id_2
> --+---++
> 1 | 1 | 1 | 3
> 1 | 2 | 1 | 3
>
> I expected for min_c_id in the second row 3.
Which it is if you turn enable_indexscan to off
The following bug has been logged online:
Bug reference: 4290
Logged by: Andreas
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.3
Operating system: Linux
Description:wrong double subselect with aggregate function
Details:
select version() ;
