[Enhancement]: hypertable-based enable and disable functions for policies

[JamesGuthrie]

What type of enhancement is this?

API improvement

What subsystems and features will be improved?

Background worker

What does the enhancement do?

Currently, if I want to disable the compression policy for a hypertable, I have to run the following query:

SELECT public.alter_job(j.id, scheduled => false)
FROM _timescaledb_config.bgw_job j
JOIN _timescaledb_catalog.hypertable h ON h.id = j.hypertable_id
WHERE j.proc_schema IN ('_timescaledb_internal', '_timescaledb_functions')
  AND j.proc_name = 'policy_compression'
  AND j.id >= 1000
  AND format('%I.%I', h.schema_name, h.table_name)::text::regclass = <hypertable name>::text::regclass;

It would be much nicer to do this:

SELECT disable_compression_policy(<hypertable name>);

Implementation challenges

No response

[RafiaSabih]

Well there is all new policies api built because of all such reasons only. No idea when they will mature from experimental schema. I am talking about https://docs.timescale.com/api/latest/continuous-aggregates/remove_policies/

…

On Mon, Sep 25, 2023, 18:05 James Guthrie ***@***.***> wrote: What type of enhancement is this? API improvement What subsystems and features will be improved? Background worker What does the enhancement do? Currently, if I want to disable the compression policy for a hypertable, I have to run the following query: SELECT public.alter_job(j.id, scheduled => false)FROM _timescaledb_config.bgw_job jJOIN _timescaledb_catalog.hypertable h ON h.id = j.hypertable_idWHERE j.proc_schema IN ('_timescaledb_internal', '_timescaledb_functions') AND j.proc_name = 'policy_compression' AND j.id >= 1000 AND format('%I.%I', h.schema_name, h.table_name)::text::regclass = <hypertable name>::text::regclass; It would be much nicer to do this: SELECT disable_compression_policy(<hypertable name>); Implementation challenges *No response* — Reply to this email directly, view it on GitHub <#6115>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADBNYNEKQ5ZF2INL4FQFXETX4GTVTANCNFSM6AAAAAA5GKQ5X4> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[mkindahl]

Thanks @RafiaSabih for pointing to these. I think we need to start graduating functions like this to be non-experimental.

@JamesGuthrie is adding a similar interface to simplify enabling and disabling the jobs associated with the hypertable.