Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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 suggest for this? Migrate all to timescale or have two database (Timescale for 2 tables and PG for the rest) ?


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.


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.


> 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-...

https://swarm64.com/post/postgresql-columnstore-index-intro/


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


What measurable test could I do to verify I would have improvements enabling timescale on those two tables?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: