4 ms·

We have 2 tables that are good candidates for Timescales, others are fine with Postgres. We perform joins query across those 2 table and others. What do you su

• dominotw 5y ago
  > good candidates for Timescales By this i assume you want columnar access along time dimension. There are a bunch of columnar options out there ( timescale being one). you can operate hybrid row + column access. https://www.citusdata.com/blog/2021/03/06/citus-10-columnar-compression-for-postgres/ https://www.citusdata.com/blog/2021/03/06/citus-10-columnar-... https://swarm64.com/post/postgresql-columnstore-index-intro/ https://swarm64.com/post/postgresql-columnstore-index-intro/
• devops000 5y ago
  What measurable test could I do to verify I would have improvements enabling timescale on those two tables?
• Croftengea 5y ago
  TimescaleDB is a PostgreSQL extension, so you don't have to choose. Just convert these two tables to hyper-tables and leave the rest as is.
• chrisdalke 5y ago
  As far as I know, you can seamlessly join Timescale tables with normal Postgres tables in a query. Timescale is activated on a per-table basis.
• Jarwain 5y ago
  Does your postgres host allow you to install the timescale extension? If so, I'd go with that and specify the two tables as being hypertables. If not, it may be worthwhile to migrate to a host that Does support timescaledb, if not timescales managed product itself