Thanks for trying out TimescaleDB. Glad you're having a good experience. :)
We think that declarative partitioning is a great step forward for Postgres partitioning. That said the process is still quite manual (including in PG11) -- unless I am mistaken, auto-creating partitioned tables is not in PG11, but perhaps may get released with PG12 at the end of 2019.
But even with auto-creating partitioned tables, TimescaleDB is still necessary for a few reasons:
- Support for multiple time-based query optimization in the planner
- More efficient handling of both queries and inserts when there are many partitions,
- Time-based analytical function like time_bucket,
- Support for changing partition sizes, etc.
We are also working on many new features, optimizations, and capabilities slated for the next year which will improve time-series workloads in PostgreSQL even more.
Comments
Thanks for trying out TimescaleDB. Glad you're having a good experience. :)
We think that declarative partitioning is a great step forward for Postgres partitioning. That said the process is still quite manual (including in PG11) -- unless I am mistaken, auto-creating partitioned tables is not in PG11, but perhaps may get released with PG12 at the end of 2019.
But even with auto-creating partitioned tables, TimescaleDB is still necessary for a few reasons:
- Support for multiple time-based query optimization in the planner
- More efficient handling of both queries and inserts when there are many partitions,
- Time-based analytical function like time_bucket,
- Support for changing partition sizes, etc.
We are also working on many new features, optimizations, and capabilities slated for the next year which will improve time-series workloads in PostgreSQL even more.