Re: [HACKERS] Problem with multiple SUMs - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] Problem with multiple SUMs
Date
Msg-id 199901271616.LAA08811@candle.pha.pa.us
Whole thread Raw
In response to Re: [HACKERS] Problem with multiple SUMs  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Fixed.


> "D'Arcy" "J.M." Cain <darcy@druid.net> writes:
> > After recent changes I find an error with SUM when summing more than
> > one column. ...
> > See how the individual sums are correct but I can no longer get both
> > sums in one select.
> 
> Good eye!
> 
> Actually, it looks like *any* two aggregates conflict --- we're
> reporting the result of the rightmost aggregate for all aggregate
> functions in a SELECT.  Using D'Arcy's test table, I also tried
> 
> treetest=> SELECT AVG(a), SUM(a) FROM x;
> avg|sum
> ---+---
>   3|  3
> (1 row)
> 
> treetest=> SELECT AVG(a), SUM(b) FROM x;
> avg|sum
> ---+---
>  12| 12
> (1 row)
> 
> treetest=> SELECT AVG(a), COUNT(b) FROM x;
> avg|count
> ---+-----
>   2|    2
> (1 row)
> 
> Oops.
> 
> This bug appears to explain some of the regression-test failures I'm
> seeing --- numerology and select_having both contain multiple-aggregate
> commands that are failing.
> 
> In the select_having test, it looks like multiple aggregates used in
> the HAVING clause of a SELECT are suffering the same sort of fate
> as those in the target list.
> 
>             regards, tom lane
> 
> 


--  Bruce Momjian                        |  http://www.op.net/~candle maillist@candle.pha.pa.us            |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Re: Non-blocking queries in postgresql
Next
From: Bruce Momjian
Date:
Subject: TEMP tables