How is this on HN frontpage?
TimescaleDB 2.7 vs. PostgreSQL 14
51–56 of 56 posts
Re: TimescaleDB 2.7 vs. PostgreSQL 14
#52Earlier quoted context omitted.
Since the Timescale License is not an open source license, it is a closed source license. You are right, it is source available, but source available is also closed source. It is closed because it is not open. And it might be free as in beer, but it is not free as in freedom.
My recollection is that the TS license simply has protection against using the TS code to compete with TS, ala Amazon RDS. While some people on HN feel that this is an impurity they can’t live with, I personally think it’s a small price to pay to enable development of TS to continue. In my opinion, claiming that it’s closed source is somewhat dogmatic. Many open source licenses have some kind of restrictions on use;…
Re: TimescaleDB 2.7 vs. PostgreSQL 14
#53Earlier quoted context omitted.
Since the Timescale License is not an open source license, it is a closed source license. You are right, it is source available, but source available is also closed source. It is closed because it is not open. And it might be free as in beer, but it is not free as in freedom.
Ah, I suppose you'd prefer they switched to Affero GPL v3 (which BTW IS open source and written by FSF itself) - check it out here: https://www.gnu.org/licenses/agpl-3.0.en.html This license turns out to be very difficult to use for almost developer.
Re: TimescaleDB 2.7 vs. PostgreSQL 14
#54Re: TimescaleDB 2.7 vs. PostgreSQL 14
#55Love TimescaleDB, actually used it for one of our recent product feature launches: https://webapp.io/blog/storing-millions-of-vm-metrics-with-t...
Re: TimescaleDB 2.7 vs. PostgreSQL 14
#56Whenever I see these posts from TimescaleDB, I always want to ask them how it compares in performance to alternative extensions that implement the same features, rather than just comparing TimescaleDB to vanilla PostgreSQL. For example, they mention their automated data retention and how it's achieved with one SQL command, and how DELETEing records is a very costly operation, and how "even if you were using Postgres…
Seconded. I understand that Timescale extends Postgres, but I'd still like to see performance comparisons relative to other time-series databases such as InfluxDB or even TiDB. Shameless self-plug: we're also building database technology, but for embedding vectors ( https://milvus.io ) rather than time-series data - when doing query performance comparisons, we get several orders of magnitude of performance improvemen…
https://valyala.medium.com/high-cardinality-tsdb-benchmarks-...