Migrate continuous aggregates

Migrate your continuous aggregates to the new format introduced in TimescaleDB 2.7

In v2.7 and later, s use a new format that improves performance and makes them compatible with more SQL queries. s created in older versions of , or created in a new version with the option timescaledb.finalized set to false, use the old format.

To migrate a from the old format to the new format, you can use this procedure. It automatically copies over your data and policies. You can continue to use the while the migration is happening.

Connect to your database and run:

CALL cagg_migrate('<CONTINUOUS_AGGREGATE_NAME>');

There are known issues with cagg_migrate() in version 2.8.0. Upgrade to version 2.8.1 or later before using it.

Configure continuous aggregate migration

The migration procedure provides two boolean configuration parameters, override and drop_old. By default, the name of your new is the name of your old , with the suffix _new.

Set override to true to rename your new with the original name. The old is renamed with the suffix _old.

To both rename and drop the old entirely, set both parameters to true. Note that drop_old must be used together with override.

Check on continuous aggregate migration status

To check the progress of the migration, query the migration planning table:

SELECT * FROM _timescaledb_catalog.continuous_agg_migrate_plan_step;