hi hn, hydra ceo here<p>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.<p>demo video (5 min): <a href="https://youtu.be/1yzxgb0Oyrw" rel="nofollow noreferrer">https://youtu.be/1yzxgb0Oyrw</a>
github repo: <a href="https://github.com/hydradatabase/hydra">https://github.com/hydradatabase/hydra</a><p>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.<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 changing code.<p>for testing, try the hydra free tier to create a column postgres instance on the cloud. <a href="https://dashboard.hydra.so/signup">https://dashboard.hydra.so/signup</a>
Congrats on the 1.0 Release, big milestone.<p>I'm personally really excited about all of the recent tooling for postgres aggregates. Definitely a pain point for a lot of developers and its easy to fall in trap where things work fine in the beginning and then query times explode as requirements change and the dataset grows. Nice to not have to spin up another DB in order to solve the problem as well.
What's the workflow for leveraging this extension in real-time for an existing database?<p>Say I wanted to use this to create a high performance "aggregation" API of my existing "write heavy" tables.<p>Is there a way to keep a `heap` & `columnar` table in sync?<p>(relative Postgres noob here)
I've been using Hydra for the last ~2 months & genuinely love it. The team is really talented & it's so great to see the progress they've been making. Congrats on the 1.0 GA release! Huge step!
Nice tool, only unfortunate name, consider changing it. Already very well know security tool named hydra <a href="https://github.com/vanhauser-thc/thc-hydra">https://github.com/vanhauser-thc/thc-hydra</a> been around since 2001. Then facebook went ahead and named their config tool hydra <a href="https://github.com/facebookresearch/hydra">https://github.com/facebookresearch/hydra</a> on top of it. Like we get it, hydra popular mythology but we could use more original naming for tools
Big congrats on 1.0! Super exciting project.<p>My dream scenario would be installing hydra as an extension into my main rails application database. My usecase is showing analytics numbers directly to users, like "how many people visited my listing", which regular row-level postgres is not suited to answer. To do this now we need a to get that data from our DW, which is slow for single queries, so we need a cache, which we need to keep in sync, which is complexity I don't want. It would be amazing if I could do user-facing analytics queries directly in my main app db.<p>What put me off after a quick scroll:<p>Installing the extension changes the default table type to be columnar. I don't want an installed extension to do that, my main workload is still row oriented oltp, I only want specific tables to be columnar and I don't want to change all my normal migrations to specify `USING heap`. IMO timescale does this really well, it's an extension, not a new database. At least that's how I would want it to be.<p>It also seems like you're trying to claim postgres foreign data wrappers as "hydra external tables", implying it's a new feature? Postgres does this (reading other databases and external files) out of the box and it feels sneaky to try and brand that.<p>Also the FAQ says "Hydra is not a fork." When the engine clearly is: <a href="https://github.com/hydradatabase/citus">https://github.com/hydradatabase/citus</a> I realize you want to monetize this as a bigger platform and that's completely fair, but it strikes me as dishonest to deny the citus originins in the FAQ.
Congratulations!<p>Please also add this info :<p>#1. to the pgsql-announce list: <a href="https://www.postgresql.org/search/?m=1&ln=pgsql-announce&q=hydra" rel="nofollow noreferrer">https://www.postgresql.org/search/?m=1&ln=pgsql-announce&q=h...</a> "Your search for hydra returned no hits."<p>#2. to the <a href="https://planet.postgresql.org/" rel="nofollow noreferrer">https://planet.postgresql.org/</a>
Watch out. There used to be another Hydra project, a data repository with rich linked metadata, that changed its name after legal threat over trademark from Hydra Corporation. Now it's called Hyku, <a href="https://hyku.samvera.org/" rel="nofollow noreferrer">https://hyku.samvera.org/</a><p>I hope you choose to defend your name.
Should have mentioned, if you want to chat about open source, analytics, or meet some of the Hydra team swing by our event in SF this Thursday: <a href="https://partiful.com/e/gowvDVdnNcBLKUzfGOPv" rel="nofollow noreferrer">https://partiful.com/e/gowvDVdnNcBLKUzfGOPv</a>
some previous discussions:<p><a href="https://news.ycombinator.com/item?id=37247945">https://news.ycombinator.com/item?id=37247945</a><p><a href="https://news.ycombinator.com/item?id=36987920">https://news.ycombinator.com/item?id=36987920</a><p>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 <<a href="https://github.com/hydradatabase/hydra#license">https://github.com/hydradatabase/hydra#license</a>> since the GitHub sidebar is misleading
Congratulations. @coatue, it would be great if you can share your email to reach out for Licensing details. I did fill up your form in site, but never received any response
I have 2 questions.<p>1. Is this optimized for constantly adding and removing rows to the columnar table?<p>2. Is this supported by Microsoft Azure Flexible Server for Postgres?