Create a policy that automatically refreshes a continuous aggregate. To view the policies that you set or the policies that already exist, see informational views.
|REGCLASS||The continuous aggregate to add the policy for|
|INTERVAL or integer||Start of the refresh window as an interval relative to the time when the policy is executed. |
|INTERVAL or integer||End of the refresh window as an interval relative to the time when the policy is executed. |
|INTERVAL||Interval between refresh executions in wall-clock time. Defaults to 24 hours|
|TIMESTAMPTZ||Time the policy is first run. Defaults to NULL. If omitted, then the schedule interval is the intervalbetween the finish time of the last execution and the next start. If provided, it serves as the origin with respect to which the next_start is calculated|
|TEXT||A valid time zone. If |
start_offset should be greater than
You must specify the
end_offset parameters differently,
depending on the type of the time column of the hypertable:
- For hypertables with
DATEtime columns, set the offset as an
- For hypertables with integer-based timestamps, set the offset as an
NULL is possible, it is not recommended. By default, querying a continuous aggregate returns data between
end_offset and the current time. There is no need to set
NULL. To learn more about how continuous aggregates use real-time aggregation, see the real-time aggregation section.
|BOOLEAN||Set to |
|INTEGER||TimescaleDB background job ID created to implement this policy|
Add a policy that refreshes the last month once an hour, excluding the latest hour from the aggregate. For performance reasons, we recommend that you exclude buckets that see lots of writes:
SELECT add_continuous_aggregate_policy('conditions_summary',start_offset => INTERVAL '1 month',end_offset => INTERVAL '1 hour',schedule_interval => INTERVAL '1 hour');
Found an issue on this page?Report an issue!