News for hackers. Stuff that matters.
Re:First release candidate for TimescaleDB 1.0 by comboy on Wednesday September 19, 2018 @04:54PM (#18027628)
Where does the limitation come from? Or is it just the amount of data that it's been tested on?
Re:First release candidate for TimescaleDB 1.0 by mfreed on Wednesday September 19, 2018 @05:53PM (#18027989)
TimescaleDB clustering is currently limited to a single primary with multiple read-only replicas (which provide both HA failover and scaling concurrent reads).

So the limitation here is the storage capacity available for the nodes, and so the above reflects the amount of data we've seen in use in various RAIDed or network-attached storage environments (like the cloud).

One interesting thing here is that you can "elastically" add a new disk to a existing hypertable, and new writes will be automatically load balanced across the new disk. (In Postgres speak, we support multiple tablespaces in a single hypertable, and we allow you to dynamically add a new tablespace to an existing one: https://docs.timescale.com/api#attach_tablespace )

Re:First release candidate for TimescaleDB 1.0 by cevian on Wednesday September 19, 2018 @05:52PM (#18027979)
The latter. Because of the table partitioning there is not much dependency between old and new data so we've seen consistent performance as you add more and more data.