Storing messages in external (non-SQL) storage would be highly beneficial. The tc_positions
table, which stores GPS messages (essentially immutable timestamped logs), is growing rapidly. Timeseries databases would be far more efficient for this append-only/read-heavy workload. Is timeseries storage support planned for the future?
We already support timeseries database. I recommend checking our blog posts.
Thanks for your work! I always checked Github releases, but there was no information about new features in them. TimescaleDB is what I need, partitioning should work in the long run, thanks again!
Storing messages in external (non-SQL) storage would be highly beneficial. The
tc_positions
table, which stores GPS messages (essentially immutable timestamped logs), is growing rapidly. Timeseries databases would be far more efficient for this append-only/read-heavy workload. Is timeseries storage support planned for the future?