Re: BUG #17961: Incorrect aggregation MIN, AVG, MAX

Поиск
Список
Период
Сортировка
Искать
От
Julien Rouhaud
Тема
Re: BUG #17961: Incorrect aggregation MIN, AVG, MAX
Дата
Msg-id
20230605074042.qs57ybyvrazkvhcp@jrouhaud
Ответ на
Список
Дерево обсуждения
BUG #17961: Incorrect aggregation MIN, AVG, MAX PG Bug reporting form <noreply@postgresql.org>
Re: BUG #17961: Incorrect aggregation MIN, AVG, MAX Julien Rouhaud <rjuju123@gmail.com>
Re: BUG #17961: Incorrect aggregation MIN, AVG, MAX Maxim Zakharov <dp.maxime@gmail.com>
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?


В списке pgsql-bugs по дате отправления
От: Nikhil Benesch
Дата:
От: Maxim Zakharov
Дата:
FAQ