This is a thought exercise I've done myself, and your questions will mostly be answered by looking at the features (https://docs.timescale.com/api/latest/ https

This is a thought exercise I've done myself, and your questions will mostly be answered by looking at the features (https://docs.timescale.com/api/latest/ https://docs.timescale.com/api/latest/) that TimescaleDB provides. > However, this basically means a compressed column store, which again, doesn't really have much to do with time. It does though: which data do you compress? The old data. Why not let the database figure that out for you, so you don't specifically have to tell it. Other features include: - Continuous Aggregates: a materialized view aggregating data over time is doable, but why not let the database materialize it for you, and automatically fall back to an un-materialized query for the newest data? - Retention: deleting (or downsampling) old data is easy to do on your own, but why not let the database do it for you according to a policy?