hi hn, hydra ceo here<p>hydra is an open source, column-oriented postgres. you can set up remarkably fast aggregates on your project in minutes to query billions of rows instantly.<p>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 making code changes. data is automatically loaded into columnar format and compressed. connect to hydra with your preferred postgres client (psql, dbeaver, etc).<p>following 4 months of development on hydra v0.3.0-alpha, our team is proud to share our first major version release. hydra 1.0 is under active development, but ready for use and feedback. we’re aiming to release 1.0 into general availability (ga) soon.<p>for testing, try the hydra free tier to create a column-oriented postgres instance on the cloud. <a href="https://dashboard.hydra.so/signup">https://dashboard.hydra.so/signup</a>
Congratulations!<p>Can we expect support for gist, gin, spgist, and brin indexes sometime in the near future?<p>Based on the source code, it appears that they are not supported:<p><a href="https://github.com/hydradatabase/hydra/blob/96056312e7c0f4135e31ce5380f4f7b4cfb7b42f/columnar/src/backend/columnar/README.md?plain=1#L190">https://github.com/hydradatabase/hydra/blob/96056312e7c0f413...</a><p><i>"... Columnar supports `btree` and `hash `indexes (and
the constraints requiring them) but does not support `gist`, `gin`,
`spgist` and `brin` indexes."</i>
Congrats on the launch!<p>For those who have not experimented with columnar based databases, I would highly recommend toying around with them.<p>The performance improvements can be substantial. Obviously there are drawbacks involved with integrating a new database into your infrastructure, so it is exciting to see columnar format introduced to Postgres. Removes the hurdle of learning, deploying and monitoring another database.
Talked to OP last night and played around with it this morning. This is something I've wanted to see added to postgres for a long time, and couldn't have been done by a nicer and more accommodating founder. Very excited.
Congrats on the 1.0 milestone!<p>A few months ago, we worked with the team to bring Hydra to Jupyter, you can check out the tutorial here: <a href="https://docs.hydra.so/analyze/jupyter">https://docs.hydra.so/analyze/jupyter</a><p>JupySQL's GitHub: <a href="https://github.com/ploomber/jupysql">https://github.com/ploomber/jupysql</a>
awesome project - and we tested Zing Data ( <a href="http://www.zingdata.com" rel="nofollow noreferrer">http://www.zingdata.com</a> ) with Hydra to make really fast analytical queries on postgres scale to analytics users on mobile and so far have seen great results.
This looks really impressive, and I'm excited to see how it performs on our data!<p>P.S., I think the name conflicts with Hydra, the configuration management library: <a href="https://hydra.cc/" rel="nofollow noreferrer">https://hydra.cc/</a>
I would love to have the ability to define "column groups" in regular Postgres. For example most of the time I just leave the table row-oriented, but when trying to optimize performance of specific tables and queries I could tell postgres to store one or a handful of columns separately similar to a column oriented database. This would allow getting quite a bit of performance out of my database for the few cases in OLTP where I need to do some scans or searches. Even just breaking out some rarely used columns into a separate group could be quite nice for keeping the caches hot.
From my initial 5 minutes of getting setup with an existing install, it's all fairly easy.<p># Requirements<p><pre><code> - lz4
- zstd
</code></pre>
# Building<p><pre><code> git clone https://github.com/hydradatabase/hydra
cd hydra/columnar
./configure
make
make install
</code></pre>
# Install<p><pre><code> CREATE EXTENSION IF NOT EXISTS columnar;
</code></pre>
The actual extension docs are at <a href="https://docs.hydra.so/concepts/using-hydra-columnar">https://docs.hydra.so/concepts/using-hydra-columnar</a>
Very out of touch with Postgres, but is there a native column oriented table type option in Postgres so that you choose either row-based or columnar in the CREATE TABLE DDL?
Congrats to the entire Hydra team on the launch! We (Artemis - <a href="https://www.artemisdata.io/" rel="nofollow noreferrer">https://www.artemisdata.io/</a>) are stoked to be build with you as a partner to help data teams analyze data even faster!
super impressive performance improvements!<p>do most of your customers replicate their postgres database to Hydra for analytics jobs, or what's the typical set up?
I wanted to say thank you for using actual Open Source licenses. It's gotten to where I treat any recent "Launch HN" or "Show HN" containing "open source" in the title as "well, I wonder which crazy license this project is using"