columnar

Just wonder what is the advantage of Redshift vs using something such as https://github.com/hydradatabase/columnar, if we are already using postgres?

for one thing, depending on your licensing contraints: - Citus is AGPLv3 https://github.com/citusdata/citus/blob/v13.0.1/LICENSE - Hydra is Apache 2 https://github.com/hydradatabase/columnar/blob/v1.1.2/LICENS... - Timescale is mostly Apache 2 https://github.com/timescale/timescaledb/blob/2.18.2/LICENSE

re: columnar - https://github.com/hydradatabase/hydra/tree/main/columnar a much updated fork of citus' columnar using Postgres tableam. re: duckdb handling storage - https://github.com/hydradatabase/pg_quack/tree/branch-0.0.1 an earlier implementation

Don't feel bad, lots of people get bitten by not reading all the way down to the bottom of their readme: https://github.com/hydradatabase/hydra/blob/v1.1.2/README.md... While Hydra may very well license their own code Apache 2, they ship the AGPLv3 columnar which to my very best IANAL understanding taints the whole stack and AGPLv3's everything all the way through https://github.com/hydradatabase/hydra/blob/v1.1.2/columnar/...

for others curious ParadeDB - AGPL License https://github.com/paradedb/paradedb/blob/dev/LICENSE Hydra - Apache 2.0 https://github.com/hydradatabase/hydra/blob/main/LICENSE also hydra seems derived from citusdata's columnar implementation.

Columnar store PostgreSQL extension exists, here are two but I think I’m missing at least another one: https://github.com/citusdata/cstore_fdw https://github.com/hydradatabase/hydra You can also connect other stores using the foreign data wrappers, like parquet files stored on an object store, duckdb, clickhouse… though the joins aren’t optimised as PostgreSQL would do full scan on the external table when joining.

New column store alternative : https://github.com/hydradatabase/hydra HN: https://news.ycombinator.com/item?id=37571974

some previous discussions: https://news.ycombinator.com/item?id=37247945 https://news.ycombinator.com/item?id=36987920 and a relevant observation is that there are actually multiple license files in the repo so the consumer should read their explicit licensing section of the readme <https://github.com/hydradatabase/hydra#license> since the GitHub sidebar is misleading

hi hn, hydra ceo here hydra is an open-source extension that adds columnar tables to Postgres for efficient analytical reporting. With Hydra, you can analyze billions of rows instantly without changing code. demo video (5 min): https://youtu.be/1yzxgb0Oyrw github repo: https://github.com/hydradatabase/hydra For 1.0 GA release, aggregate queries are over *60% faster* than Hydra beta due to aggregate vectorization. Spatial indexes (gin, gist, spgist, and rum indexes) and pg_hint_plan are now enabled for performance optimization. postgres is great, but aggregates can take minutes to hours to return results on large data sets. long-running analytical queries hog database resources and degrade performance. use hydra to run much faster analytics on postgres without changing code. for testing, try the hydra free tier to create a column postgres

Idk, but I'd rather see a new iteration of PostgreSQL, similiar to Hydra[0], with a new engine become the upstream instead of a whole new database. There's a lot of experience about db operation and how to approach MVCC encoded in PostgreSQL that shouldn't be underestimated. [0]: https://github.com/hydradatabase/hydra

And just like last time, watch out for the misleading GitHub license detector because it's not entirely Apache as the GitHub summary claims but rather *some* is Apache and buried in the interior is some AGPL stuff: https://github.com/hydradatabase/hydra#license

From my initial 5 minutes of getting setup with an existing install, it's all fairly easy. # Requirements - lz4 - zstd # Building git clone https://github.com/hydradatabase/hydra cd hydra/columnar ./configure make make install # Install CREATE EXTENSION IF NOT EXISTS columnar; The actual extension docs are at https://docs.hydra.so/concepts/using-hydra-columnar

hydra columnar inherits its license from citus: https://github.com/hydradatabase/hydra/blob/main/columnar/LI... but, hydra itself is more than just the columnar extension.

Congratulations! Can we expect support for gist, gin, spgist, and brin indexes sometime in the near future? Based on the source code, it appears that they are not supported: https://github.com/hydradatabase/hydra/blob/96056312e7c0f413... "... Columnar supports `btree` and `hash `indexes (and the constraints requiring them) but does not support `gist`, `gin`, `spgist` and `brin` indexes."