[jauntywundrkind]

Clickhouse also just put out a fun article on scaling pgbouncer too, talking about scaling out so_reuseport while not having to shard so harshly (a major limitation pgdog here is addressing via rewrite), https://clickhouse.com/blog/pgbouncer-clickhouse-managed-pos... https://news.ycombinator.com/item?id=48814152

[merb]

Well tbf pgdog looks extremely amazing on paper and goes way beyond multi threading.

The notify/listen fix and automatic query routing to read replicas and auto sharding might bringt Postgres finally closer to vitess

[khurs]

>might bringt Postgres finally closer to vitess

Supabase are launching a Vitess for Postgresql, they have hired the original creator of Vitess for it

https://supabase.com/blog/multigres-vitess-for-postgres

[tpetry]

And Planetscale (who is the current primary maintainer of vitess) is developing a Vitess for PostgreSQL.

There will be a couple of production-grade PG vitess solutions the next months.

[khurs]

Looked it up, says 'Will be released as an open source project' but announcement was in July 2025 and no public repo yet which is strange, so time will tell if they will stick to this.

https://planetscale.com/blog/planetscale-for-postgres#vitess...

https://planetscale.com/neki

...

Supabase one is open from start:

https://github.com/multigres/multigres

https://multigres.com/

[samlambert]

We are already moving Neki customers into production. Nobody else is even close. PlanetScale doesn't spend our days yapping about what we are going to do. We just do it.

[khurs]

Congrats!

The question was whether your previous statement about it being open source was still the case, or is it now going to be propriety?

[timacles]

Famous last words.

There will be 0 production grade solutions in the next months, I guarantee it