Scaling Breakthrough: EPAS 17 Scales Twice as Well, Thanks PostgreSQL

Just to add a little context for those that don't read the article: this jump in scaling performance actually comes from PostgreSQL's improvements from 16 to 17. EDB's Postgres distributions just follow community PostgreSQL extremely closely, so we're able to take advantage of the huge improvements made by the open source PostgreSQL community.

This really is a big thing. Same hardware, same workload, double the performance. That doesn't happen often, especially for a project that got its start in the 1980s and is still growing today.

It's pretty wild what they've managed to pull off. I've been tinkering with it, and honestly, I'm kinda blown away. What I find cool is that it's not just for the big players. Even if you're running a smaller setup, this could be a nice upgrade. And if you're still on the fence about moving away from Oracle, this might make that decision a bit easier.

Kudos to the writer for shedding light on these remarkable improvements! A big thank you to the PostgreSQL community for their continuous innovation and to EDB for pushing boundaries with EPAS 17. These advancements are vital for scaling modern platforms—excited to see how these enhancements drive future workloads. Great work!

It seems rather unfair this post didn't do well given the clearly gushing comments in this thread by brand new accounts.