<![CDATA[TimeScale and drop_chunks, DCI disk usage]]>Anyone else using timescaledb with postgres?

When I look at timescaledb maintenance, typically the drop_chunks function would be used to reclaim disk space. However, drop_chunks requires TIMESTAMP, TIMESTAMPTZ, or DATE column types. For 'idata' and 'tdata', for example, the timestamp column is actually an int4.

Any pointers on how to determine whether NetXMS is actually pruning old entries to reclaim disk space? It's certainly dropping DCIs correctly from an access standpoint -- queries only return the expected time ranges.

]]>https://forum.netxms.org/topic/6086/timescale-and-drop_chunks-dci-disk-usageRSS for NodeFri, 13 Nov 2026 17:39:15 GMTWed, 14 Aug 2019 16:40:43 GMT60<![CDATA[Reply to TimeScale and drop_chunks, DCI disk usage on Tue, 20 Aug 2019 12:57:32 GMT]]>Yes, NetXMS uses explicit cutoff points for dropping chunks. But please note that TimescaleDB support in 2.2.16 is quite immature - we have improved it significantly in 3.0 branch.

Best regards,
Victor

]]>https://forum.netxms.org/post/26313https://forum.netxms.org/post/26313Tue, 20 Aug 2019 12:57:32 GMT<![CDATA[Reply to TimeScale and drop_chunks, DCI disk usage on Wed, 14 Aug 2019 22:42:54 GMT]]>drop_chunks requires TIMESTAMP, TIMESTAMPTZ or DATE if the cut-off point is set as an interval.
If the cut-off point is given explicitly, you can use integers, see https://docs.timescale.com/latest/api#drop_chunks
As NetXMS uses integers in its current cleanup queries, I would assume it will use explicit cut-off points for drop_chunks as well.
Note that I'm not a dev and haven't looked at the code...

]]>https://forum.netxms.org/post/26277https://forum.netxms.org/post/26277Wed, 14 Aug 2019 22:42:54 GMT