time_partitioning_func described here: Timescale Docs
We want to use
timestamp9 as time column and everything works, besides
add_compression_policy (because it manipulates with the time column type and doesn’t know about timestamp9 extension). We though that it would be interesting to use
time_partitioning_func to convert timestamp9 to bigint and use bigints in chunk_intervals/compression_policies
Question: does this
time_partitioning_func functionality affects only chunk management/policies and does not affect regular queries performance?
P.S. Currently, we are choosing between adding custom jobs (with add_compression_policy behaviour) for
timestamp9 tables and this.
With warm regards,