Compression policies on continuous aggregates

Before setting up a compression policy on a continuous aggregate, you should set up a [refresh policy][refresh-policy]. The compression policy interval should be set so that actively refreshed regions are not compressed. This is to prevent refresh policies from failing. For example, consider a refresh policy like this:

With this kind of refresh policy, the compression policy needs the compress_after parameter greater than the start_offset parameter of the continuous aggregate policy:

===== PAGE: https://docs.tigerdata.com/use-timescale/compression/manual-compression/ =====

Examples:

Example 1 (sql):

ALTER MATERIALIZED VIEW cagg_name set (timescaledb.compress = true);

Example 2 (sql):

ALTER MATERIALIZED VIEW cagg_name set (timescaledb.compress = false);

Example 3 (sql):

SELECT decompress_chunk(c, true) FROM show_chunks('cagg_name') c;

Example 4 (sql):

SELECT add_continuous_aggregate_policy('cagg_name',
  start_offset => INTERVAL '30 days',
  end_offset => INTERVAL '1 day',
  schedule_interval => INTERVAL '1 hour');