4 ms·
Unfortunately Timescale's license is the blocker - https://news.ycombinator.com/item?id=25299128 https://news.ycombinator.com/item?id=25299128
by Aarvay 5y ago
Unfortunately Timescale's license is the blocker - https://news.ycombinator.com/item?id=25299128 https://news.ycombinator.com/item?id=25299128
- kiwicopple 5y agoyes, we'd love to offer Timescale as an extension, but still waiting for buy-in from the Timescale team on this. If we can't manage we'll eventually do something else for timeseries data - eg, we could do a Foreign Data Wrapper to Clickhouse tables
- qoega 5y agoWhy use FDW if you can work with ClickHouse directly? What is the use case? By the way I can see there are some already but I do not use them https://github.com/Infinidat/infi.clickhouse_fdw/ https://github.com/Infinidat/infi.clickhouse_fdw/ https://github.com/adjust/clickhouse_fdw https://github.com/adjust/clickhouse_fdw
- kiwicopple 5y ago> Why use FDW It would be beneficial to couple transactional data (Postgres) with OLAP data (CH). There are a few other things coming in PG which might mitigate the need for CH too (pluggable storage, zheap), so we're not going to rush this part.