Hacker News Reader

Comment by gfody | Hacker News Reader

clickhouse is more generally olap and not suitable for oltp, you could call it an olap+timeseries solution similarly to how you position timescale as oltp+timeseries (not all olap solutions support timeseries well but clickhouse does, though their actual positioning is modest: https://clickhouse.com/docs/en/faq/use-cases/time-series)

how much of timescale's performance would you say is inherited from PostgreSQL?

View on HN

    clickhouse is more generally olap and not suitable for oltp, you could call it an olap+timeseries solution similarly to how you position timescale as oltp+timeseries

You are correct, TimescaleDB is time-series + OLTP. But I would argue that ClickHouse is just OLAP, but is better at time-series than other OLAP. But maybe now I am splitting hairs (and my apologies if I am).

   how much of timescale's performance would you say is inherited from PostgreSQL?

The performance areas where TimescaleDB shines is mostly stuff we have built. But the reliability, tooling, and ecosystem are mostly inherited from Postgres (which I think is a very good thing)

Reply on news.ycombinator.com