The advantage on inserts with TimescaleDB is the automation. The built-in way on Postgres still requires a lot of manual maintenance, especially as data patterns change. TimescaleDB adjusts automatically.

(Nothing against Postgres - it just that Postgres needs to design for the general use case, while we can optimize for time-series.)

But TimescaleDB is much more than automatic partitioning. You also get:

* 15x native compression (95%+ storage savings) [0]

* Faster queries for time-series (b/c of our optimizations at the query planning / execution level)

* Automatic data retention policies (for automatically deleting old data) [1]

* Continuous aggregates (real-time materialized views automatically refreshed) [2]

(and lots more)

Happy to answer any more questions!

[0] https://docs.timescale.com/latest/using-timescaledb/compress...

[1] https://docs.timescale.com/latest/using-timescaledb/data-ret...

[2] https://docs.timescale.com/latest/using-timescaledb/continuo...