pg_timeseries: Open-source time-series extension for PostgreSQL • Hacker News Board

Re: pg_timeseries: Open-source time-series extension for PostgreSQL

#81

Post by redwood » Fri, May 24, 2024, 6:01 PM UTC

smga3000 wrote: post #78

akulkarni wrote: post #77

Earlier quoted context omitted.

Ajay, Timescale CEO and co-founder, here. It saddens me to see that we have generated so much ill will from you. It sounds like you were affected by our layoffs last year. You have every right to be upset. If you ever want to chat about this 1:1, you know how to reach me. I’d be happy to make the time. To anyone else reading this: Some of what this person has shared is true, but some of it is not true. I debated whet…

Taking responsibility for laying off a bunch of people is thin gruel. What does that mean? Nothing. They showed you loyalty, you didn't return it. The over hiring is a symptom of bad management, so taking responsibility would be to demote yourself and take a pay cut. All the executive staff should have taken one and kept more people on. It is irresponsible and cruel to overhire and then dump people. I could say more,…

Over-hiring is a calculus that shifts depending on macro market conditions. To pretend otherwise just isn't an honest assessment of what it means to be a business leader. In the zero interest rate era, it was irresponsible for business executives to not invest to ensure they had a competitive foundation or else be left-behind by those doing so... The rise of interest rates changed the market's appetite to invest in non-profitable growth companies, which in turn had a series of follow-on effects that required software executives to reverse course so as to optimize for their long term viability in the new climate.

Re: pg_timeseries: Open-source time-series extension for PostgreSQL

#82

Post by redwood » Fri, May 24, 2024, 6:02 PM UTC

techoffs wrote: post #74

Former Timescaler here. It's about time that Timescale started getting what it deserves. Sometime in early 2022, just as they raised their Series C, leadership decided that they had gotten what they wanted from the open-source community and TimescaleDB. They decided it was time to focus 100% on Timescale Cloud. Features began to become exclusive to Timescale Cloud, and the self-hosted TimescaleDB was literally treate…

Knowing little about the company, it's almost certainly completely untrue to state the "the company was highly profitable"; you don't hire 160 people in an OSS-centric business and also turn a profit. You likely have a distorted understanding of the challenging nature of the burn rate in a changing macro environment.

Re: pg_timeseries: Open-source time-series extension for PostgreSQL

#83

Post by remram » Fri, May 24, 2024, 9:41 PM UTC

riedel wrote: post #6

>You may already be asking: “why not just power the stack using TimescaleDB?” The Timescale License would restrict our use of features such as compression, incremental materialized views, and bottomless storage. With these missing, we felt that what remained would not provide an adequate basis for our customers’ time-series needs. Therefore, we decided to build our own PostgreSQL-licensed extension. Have been using t…

500 million observations, with 4-byte floats, is 2 GB. This is the kind of size that you can store uncompressed, in RAM, on a phone. It is hardly at the point where you require specialized time-series software at all.

Re: pg_timeseries: Open-source time-series extension for PostgreSQL

#84

Post by smythe123 » Sat, Jun 01, 2024, 9:34 AM UTC

nikita wrote: post #34

nitinreddy88 wrote: post #18

Earlier quoted context omitted.

Looking at the comparison with Click Benchmark, they are almost pathetic in terms of performance. They cant even handle sub-second aggregation queries for 10M records. Compared that too even duckdb reading from parquet files.

Postgres is missing a proper columnstore implementation. It's a big gap and it's not easy to build. One solution could be integrating duckdb in a similar way as pgvector. You need to map duckdb storage to Postgres storage and reuse duckdb query processor. I believe it's the fastest way to get Postgres to have competitive columnstores.

Olo, CEO of https://www.tablespace.io here. We've built a columnstore extension for Postgres that is faster than ClikcHouse for real-time analytics in their own ClickBench Benchmarks. Feel free to check it out - https://www.tablespace.io/blog/postgres-columnstore-index-vs...