PG Bug reporting form <noreply@postgresql.org> writes:
> Aggregate functions (described here
> https://www.postgresql.org/docs/current/functions-aggregate.html#FUNCTIONS-AGGREGATE-STATISTICS-TABLE)
> that are defined for double precision type suffer from loss of
> significance.
This is pretty much inherent in all uses of float arithmetic.
You might be happier using the numeric type (of course, that's
much slower).
Another possibility, for some aggregates, is to order the inputs
in a way that minimizes error accumulation. For example,
select sum(f1 order by abs(f1)) from ...
I don't know offhand what the best such incantation is for covar_pop;
it might depend on the problem.
regards, tom lane
