| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | dp(dot)maxime(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17961: Incorrect aggregation MIN, AVG, MAX |
| Date: | 2023-06-05 07:40:42 |
| Message-ID: | 20230605074042.qs57ybyvrazkvhcp@jrouhaud |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
On Sun, Jun 04, 2023 at 10:04:04PM +0000, PG Bug reporting form wrote:
>
> I came across a situation when MIN(), AVG() and MAX() aggregates where
> computed incorrectly, as you can see from the output below the valuer of
> MIN() is higher than AVG() and MAX()!
> Expected values should be the same as for MIN()
> The table n has all values been updated several times with different values
> and currently all rows contain the value of 11.55
>
> asx=# select at, MIN(diluted_earnings_1)::numeric as diluted_earnings_1min,
> ROUND(AVG(diluted_earnings)::numeric, 2) as diluted_earnings_1avg,
> MAX(diluted_earnings)::numeric as diluted_earnings_1max
Unless I'm missing something you're using diluted_earnings_1 for min, but
diluted_earnings for avg and max so it looks like it's working as expected?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maxim Zakharov | 2023-06-05 07:46:58 | Re: BUG #17961: Incorrect aggregation MIN, AVG, MAX |
| Previous Message | Nikhil Benesch | 2023-06-05 01:02:45 | Re: Array parsing incorrectly accepts ragged multidimensional arrays |