aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/numeric.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2020-06-13 13:43:24 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2020-06-13 13:43:40 -0400
commit03109a53020e4663df3a8d822cdc665a7d712a93 (patch)
treea4c7c98f8e90ea76f8ea34e3a36ec63b66b2dcc2 /src/backend/utils/adt/numeric.c
parentd64f1cdf2f4bef1454c74af1028c9ea0c3280322 (diff)
downloadpostgresql-03109a53020e4663df3a8d822cdc665a7d712a93.tar.gz
postgresql-03109a53020e4663df3a8d822cdc665a7d712a93.zip
Fix behavior of float aggregates for single Inf or NaN inputs.
When there is just one non-null input value, and it is infinity or NaN, aggregates such as stddev_pop and covar_pop should produce a NaN result, because the calculation is not well-defined. They used to do so, but since we adopted Youngs-Cramer aggregation in commit e954a727f, they produced zero instead. That's an oversight, so fix it. Add tests exercising these edge cases. Affected aggregates are var_pop(double precision) stddev_pop(double precision) var_pop(real) stddev_pop(real) regr_sxx(double precision,double precision) regr_syy(double precision,double precision) regr_sxy(double precision,double precision) regr_r2(double precision,double precision) regr_slope(double precision,double precision) regr_intercept(double precision,double precision) covar_pop(double precision,double precision) corr(double precision,double precision) Back-patch to v12 where the behavior change was accidentally introduced. Report and patch by me; thanks to Dean Rasheed for review. Discussion: https://postgr.es/m/353062.1591898766@sss.pgh.pa.us
Diffstat (limited to 'src/backend/utils/adt/numeric.c')
0 files changed, 0 insertions, 0 deletions