So this is based on Postgresql. How does it compared to other solutions that are written from scratch to be a time series DB like influxDB?
At a high level though, we do find that having native support for full SQL to be a big win. Also, if you already store metadata or other relational data that you want to combine with your time-series data, it's great to be able to use one DB instead of separate solutions. Performance wise we do believe we are competitive and in some cases much better, and we have the 20 years of stability from PostgreSQL to build on.
At first blush KDB is orders of magnitude faster, especially if using a GZIP card.
But Timescale is open source and not core locked.
¯\_(ツ)_/¯
Are there actual benchmarks that show KDB being orders of magnitude faster than Timescale? How many orders of magnitude are we talking about?