Re:TimescaleDB 1.0 Is Production Ready
by RobAtticus on Wednesday October 31, 2018 @03:34PM
(#18348631)
Yep, 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.
[ Parent
| on HN ]
Re:TimescaleDB 1.0 Is Production Ready
by sman393 on Wednesday October 31, 2018 @04:23PM
(#18348984)
Good to hear! how does the current TimescaleDB single node limitation play into it?
Re:TimescaleDB 1.0 Is Production Ready
by RobAtticus on Wednesday October 31, 2018 @05:47PM
(#18349540)
Not 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.
Re:TimescaleDB 1.0 Is Production Ready
by sman393 on Wednesday October 31, 2018 @09:11PM
(#18350673)
Alright thanks! I thought I read that TimescaleDB doesn't support clustering yet, only single node Postgres installs, But I could've misunderstood it.
Re:TimescaleDB 1.0 Is Production Ready
by RobAtticus on Wednesday October 31, 2018 @10:35PM
(#18351061)
It 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).