Your site is very well designed and easy to read btw, and the app UI looks great from the demo photos. I might try it!
pg_timeseries: Open-source time-series extension for PostgreSQL
11–20 of 84 posts
Re: pg_timeseries: Open-source time-series extension for PostgreSQL
#12Great to see this kind of innovation. PostgreSQL is interesting while "core" was always Open Source and using very permissive Open Source library, there have been many proprietary and source available extensions, ranging from replication to time series support.
Now we see those Proprietary extensions being disrupted by proper Open Source!
Re: pg_timeseries: Open-source time-series extension for PostgreSQL
#13Your site is very well designed and easy to read btw, and the app UI looks great from the demo photos. I might try it!
Thank you!
Re: pg_timeseries: Open-source time-series extension for PostgreSQL
#14Most of the time-series queries (almost all of them) are aggregated queries.
Why not leverage or build top-notch Columnarstore for the same.
Everything seems to be there and why there's not first class product like ClickHouse on PG.
Re: pg_timeseries: Open-source time-series extension for PostgreSQL
#15Dumb question: why can't I just insert a bunch of rows with a timestamp column and indices? Where does that fall short? At a certain # of rows or something?
What does this let me do that can't be achieved with "regular PostgreSQL without the extension"?
Re: pg_timeseries: Open-source time-series extension for PostgreSQL
#16Most of the time-series queries (almost all of them) are aggregated queries. Why not leverage or build top-notch Columnarstore for the same. Everything seems to be there and why there's not first class product like ClickHouse on PG.
Citus, Persona, TimescaleDB?
Re: pg_timeseries: Open-source time-series extension for PostgreSQL
#17Dumb question: why can't I just insert a bunch of rows with a timestamp column and indices? Where does that fall short? At a certain # of rows or something? What does this let me do that can't be achieved with "regular PostgreSQL without the extension"?
Time based partitioning.
Re: pg_timeseries: Open-source time-series extension for PostgreSQL
#18Most of the time-series queries (almost all of them) are aggregated queries. Why not leverage or build top-notch Columnarstore for the same. Everything seems to be there and why there's not first class product like ClickHouse on PG.
Citus, Persona, TimescaleDB?
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.
Re: pg_timeseries: Open-source time-series extension for PostgreSQL
#19Most of the time-series queries (almost all of them) are aggregated queries. Why not leverage or build top-notch Columnarstore for the same. Everything seems to be there and why there's not first class product like ClickHouse on PG.
The gold standard for this Druid at very large scale, or ClickhouseDB. Clickhouse has a lot of problems as far as modifying/scaling shards after the fact, while Druid handles this with ease (and the penalty of not being able to update after the fact.)
Re: pg_timeseries: Open-source time-series extension for PostgreSQL
#20Dumb question: why can't I just insert a bunch of rows with a timestamp column and indices? Where does that fall short? At a certain # of rows or something? What does this let me do that can't be achieved with "regular PostgreSQL without the extension"?
Time based partitioning.
CREATE TABLE logs (
id SERIAL PRIMARY KEY,
log_time TIMESTAMP NOT NULL,
message TEXT
) PARTITION BY RANGE (log_time);