You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PostgreSQL version (output of SELECT version();): 15.6
TimescaleDB Toolkit version (output of \dx timescaledb_toolkit in psql): 1.18.0
TimescaleDB version (output of \dx timescaledb in psql): 2.14.1
Installation method: Docker container
Describe the bug
A "double overflow" exception is unexpectedly thrown when using stats_agg to aggregate very large input values.
To Reproduce
Steps to reproduce the behavior:
Create a new database with the timescaledb and timescaledb-toolkit extensions installed.
Connect to the database using psql.
Execute the SQL statement using psql: select stats_agg(n) from (values (1e308), (1e308), (1e308)) as t(n);
Observe exception is thrown: "ERROR: called Result::unwrap() on an Err value: DoubleOverflow"
Expected behavior
No exception should be thrown; instead, the statssummary1d returned should indicate an error or overflow state, perhaps using NaN or null.
Actual behavior
Exception is thrown as described above in reproduction steps.
Screenshots
Not applicable.
Additional context
Throwing an exception appears to silently break automatic continuous aggregates updates; e.g. the problem was originally observed where input values that included "double max" (1.79769e+308) stopped all aggregation from occurring.
The text was updated successfully, but these errors were encountered:
Relevant system information:
SELECT version();
): 15.6\dx timescaledb_toolkit
inpsql
): 1.18.0\dx timescaledb
inpsql
): 2.14.1Describe the bug
A "double overflow" exception is unexpectedly thrown when using
stats_agg
to aggregate very large input values.To Reproduce
Steps to reproduce the behavior:
select stats_agg(n) from (values (1e308), (1e308), (1e308)) as t(n);
Result::unwrap()
on anErr
value: DoubleOverflow"Expected behavior
No exception should be thrown; instead, the
statssummary1d
returned should indicate an error or overflow state, perhaps usingNaN
ornull
.Actual behavior
Exception is thrown as described above in reproduction steps.
Screenshots
Not applicable.
Additional context
Throwing an exception appears to silently break automatic continuous aggregates updates; e.g. the problem was originally observed where input values that included "double max" (1.79769e+308) stopped all aggregation from occurring.
The text was updated successfully, but these errors were encountered: