From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "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 16:58:00 |
Message-ID: | 7346.1251910680@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Tom Lane wrote:
>> 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 ...
> In that light, it probably doesn't make much sense to backport the fix
> further back, given that the people (person?) bitten by the bug surely
> must already be working around it.
Yeah, and there might even be people relying on the incorrect behavior.
I'm not too worried about changing it in 8.4 since that's such a young
release, but it's a bit harder to make a case for that in older
branches.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-09-02 17:19:07 | Re: BUG #5028: CASE returns ELSE value always when type is"char" |
Previous Message | Sam Mason | 2009-09-02 16:57:19 | Re: BUG #5028: CASE returns ELSE value always when type is"char" |