Create a policy to reorder chunks on a given hypertable index in the background. (See reorder_chunk). Only one reorder policy may exist per hypertable. Only chunks that are the 3rd from the most recent will be reordered to avoid reordering chunks that are still being inserted into.
|REGCLASS||Hypertable to create the policy for.|
|TEXT||Existing index by which to order rows on disk.|
|BOOLEAN||Set to true to avoid throwing an error if the reorder_policy already exists. A notice is issued instead. Defaults to false.|
|INTEGER||TimescaleDB background job id created to implement this policy|
SELECT add_reorder_policy('conditions', 'conditions_device_id_time_idx');
creates a policy to reorder completed chunks by the existing
(device_id, time) index. (See reorder_chunk).
Found an issue on this page?Report an issue!