From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | "Sheng Y(dot) Cheng" <scheng(at)adconion(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #5025: Aggregate function with subquery in 8.3 and 8.4. |
Date: | 2009-09-02 15:36:34 |
Message-ID: | 3728.1251905794@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> Tom Lane wrote:
>> With the fix I was just about to apply, all four cases give the first
>> set of results. This clearly satisfies the principle of least
>> astonishment, at least more nearly than what we have; but it equally
>> clearly is *not* going to restore 8.4 to work just like 8.3.
> Right, 8.3 had the same underlying problem, 8.4 just makes it more
> visible as it's better at flattening subqueries.
What is interesting is that the CASE in the OP's original submission
is apparently only there to dodge the visible-since-8.0 version of
the problem; at least I can't see that it does anything else useful.
The complaint apparently is not so much that 8.3 was right, as that
the workaround for its bug stopped working ...
>> ... So I'm leaning to patching
>> 8.4 and leaving the older branches alone.
>>
>> Thoughts?
> Seems reasonable.
Will apply fix shortly --- I thought of one minor improvement to
make (the code as it stands is generating redundant PlaceHolderVars).
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Sam Mason | 2009-09-02 15:55:31 | Re: BUG #5028: CASE returns ELSE value always when type is"char" |
Previous Message | Kevin Grittner | 2009-09-02 14:52:10 | Re: BUG #5028: CASE returns ELSE value always when typeis"char" |