It's not hierarchical as you describe. You don't first partition on device, then on time. They are done simultaneously -- see this older post for an illustrat

It's not hierarchical as you describe. You don't first partition on device, then on time. They are done simultaneously -- see this older post for an illustration/comparison: https://blog.timescale.com/blog/time-series-data-postgresql-10-vs-timescaledb-816ee808bac5/#postgresql-10-partitioning https://blog.timescale.com/blog/time-series-data-postgresql-... So this architecture fully allows various striping or distribution options across time and space, even though the default might collocate chunks belonging to the same device on the same machine (at least since the last elasticity event).