PgBouncer 1.24.1 is out. It fixes CVE-2025-2291, which allowed expired passwords to still be accepted. It also fixes a few issues introduced in 1.24.0. github.com/pgbouncer/pgbo…
@MatthewSlyman@jamesacowling Which work are you referring to? Fix the security issue? Remember it is an open source project. If the extension committers don't fix it after a security report, you are free to fix it or pay someone to do it.
@eulerto@jamesacowling Yeah, but the question is, who is doing this work? And, what would happen if some volunteer software engineers helpfully wrote some enhancements, and included some vulnerabilities in that? How soon would that be spotted, as quickly as code being merged to the main project?
I love Postgres but what are areas where MySQL outperforms?
I'll start: Battle tested on mega-scale deployments, easier to control query planner with FORCE INDEX, lock fairness, better on read-heavy workloads.
What else?
@MatthewSlyman@jamesacowling You don't need to wait for the annual release to have new data types and operators. It also applies for bug fixes. This extension was written and is maintained by a Postgres committer. It works for all supported versions.
@jamesacowling Unsigned integers. There are edge cases where this matters. (MSSQL is also unable to support these; but MySQL works just fine with non-autoincrementing unsigned integers.)
True innovation comes from seeing the bigger picture:
How technology can create value through collaboration, not just competition.
We're entering an era where success comes from:
• Strategic openness
• Technology serving human progress
Not just driving efficiency...