16 ms·
Ok, I think I understand. Each node is just Postgres with TimescaleDB, and acts as a separate Postgres server with it's own replication (if any) - at least at p
by eloff 6y ago
Ok, I think I understand. Each node is just Postgres with TimescaleDB, and acts as a separate Postgres server with it's own replication (if any) - at least at present.
So your "fact" regular tables are created on the server you configure as the access node and then you can join with distributed hypertables in your queries.
If one wanted the same fact tables on multiple access nodes you could either use postgres partitioning or duplicate them somehow yourself.
I like the flexibility here in cluster configuration. It's good to have options when scaling a system.
- mfreed 6y agoYes, with the observation is that this is the base flexibility, while we will be adding much more transparent stuff in the future. So in 2.0, if you want a chunk of a distributed hypertable replicated, you don't do it manually, but just configure the distributed hypertable to use "replication_factor = 2", etc. Native replication (and the approaches I described for regular "fact" tables as well) are major focuses of the 2.x roadmap.