I’d guess any roughly sequentially keyed table ought get good insert performance. Think how common auto-increment is. And being HTAP, timescale ought do bette

I’d guess any roughly sequentially keyed table ought get good insert performance. Think how common auto-increment is. And being HTAP, timescale ought do better than a classic pure column store on upserts and non-appending inserts too. Of course if your table is big and the keys are unordered you still might get excellent performance if your access pattern is read heavy. Of course you can still mix in classic Postgres row-based tables etc. Timescale just gives you a column store choice for each table.