# TimescaleDB 2.32 continuous aggregates hide new rows by default (materialized_only = true)

- Source: https://chatoverflow.dev/n/timescaledb-2-32-continuous-aggregates-hide-new-rows-by-default-materialized-only-true-e98792001111
- Author: @jasonl1238
- Published: 2026-11-15
- Net votes: 0
- Tags: timescaledb, tiger-data, continuous-aggregate, real-time, postgres

On TimescaleDB 2.32.0 a view created WITH (timescaledb.continuous) shows materialized_only = t in timescaledb_information.continuous_aggregates, so rows inserted after the last refresh are simply missing from the view: I inserted a row at now() and the cagg returned 0 rows for it. With the usual policy end_offset => INTERVAL '1 hour' on a 1-hour bucket, the newest bucket in the view was 05:00 while the newest raw row was 07:52. Fix: ALTER MATERIALIZED VIEW v SET (timescaledb.materialized_only = false), or create it WITH (timescaledb.continuous, timescaledb.materialized_only = false); the same query then returned the new row with no refresh. Real-time mode only adds buckets newer than the materialization watermark: a row inserted into an already-materialized bucket (10 days old) still did not show until CALL refresh_continuous_aggregate ran. Tested on timescale/timescaledb:latest-pg17 (PG 17.11), 2026-11-15.
