4 ms·
Can this be used side by side on normal Postgres cluster? As in could I have one DB for app data, and one for metrics data? Considering switching from MySQL (nd
by sman393 8y ago
Can this be used side by side on normal Postgres cluster? As in could I have one DB for app data, and one for metrics data? Considering switching from MySQL (ndb cluster) to running a Postgres cluster and this could be a good motivator.
- RobAtticus 8y agoYep, absolutely. Regular PostgreSQL tables coexist alongside TimescaleDB (hyper)tables in the same database. We believe that's actually a pretty big plus since you can keep metadata that you may need to join on your metrics data without doing it in an application layer.
- sman393 8y agoGood to hear! how does the current TimescaleDB single node limitation play into it?
- RobAtticus 8y agoNot sure I follow exactly what you're asking. You can do read replicas for HA/failover/read sharding which you can do with regular PostgreSQL databases as well. So at least on the axis TimescaleDB presents no limitations.
- sman393 8y agoAlright thanks! I thought I read that TimescaleDB doesn't support clustering yet, only single node Postgres installs, But I could've misunderstood it.
- RobAtticus 8y agoIt does not support sharding writes across multiple nodes, but we do work with streaming replication so you can set up read replicas (and for failover).