Better continuous aggregates performance in TimescaleDB 2.7

TimescaleDB and PostgreSQL
2

A confusing thing is that there is no documentation saying that you cannot use OFFSET and ORIGIN in time_bucket when creating MATERIALIZED VIEW. The command will just say invalid time_bucket.

I am using TimescaleDB 2.7.0. The issue has been explained here: [Error while using origin parameter in time_bucket].
In fact, there is an open github issue too: Error creating continuous aggregate view with time_bucket origin/offset parameter · Issue #2265 · timescale/timescaledb · GitHub

Any comment?

1 Like