Hacker News new | past | comments | ask | show | jobs | submit login

I work with a lot of time series tables in Postgres, albeit not at the scale that this targets. (some millions of rows, distributed sparsely over time, on which the median insert/update size is <10, but with some tail-end inserts/updates touching >200k rows).

I like concepts behind TimescaleDB, and understand the value it's adding to vanilla Postgres. We have our own implementation at my company and it's quite good for our purposes, but it would certainly struggle at TDB's targeted scale.

As I understand it (correct me if I'm wrong, this is my impression from the marketing page), TimescaleDB is "more than an Extension" to Postgres, because it rewrites some of the Postgres internals (query parser, etc)?

If this is true, I'm curious, was it not possible to package the same results into an extension? What was the decision process like? Could the concept not be upstreamed into Postgres? I'm relatively ignorant of this side of the community, so please forgive me if this question is naive.

Finally, if it is "more than an extension", does this imply that TimescaleDB is a fork of Postgres, with all the risks to adoption that entails?

TimescaleDB is packaged as a Postgres extension. The "more than an extension" is meant to highlight that TimescaleDB makes changes and adds capabilities far beyond what the typical extension does.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact