x4m
Joined 15 years ago
Karma
153
Submissions
100
Member since
Feb 17
Postgres Hacker
View on Hacker NewsRecent submissions
Comment · 3 months ago
Was a flight to space an iteration?
Comment · 3 months ago
As Odyssey maintainer, I have to admit that it is exceptionally difficult to achieve stability (e.i. quality) of PgBouncer.
It has two limitations: it is single threaded and it is developed only re-actively. PgBouncer docs used to say that prepared statements can never be supported, in 2022 we supported it in Odyssey and then PgBouncer implemented it too.
In a sense Odyssey is developed to motivate PgBouncer development. To provide alternatives that keep PgBouncer from stagnation.
Yet, I can't say that scalability with SO_REUSEPORT is a good solution.
Comment · 3 months ago
With Odyssey we have customers with 50k+ connections operating normally.
Also consider SQPR - it's a connection pooler with sharding capabilities. It handles data migration between shard on top of request routing. Odyssey will inherit this capability once it is stable enough in functions set.
Comment · 3 months ago
Just use https://github.com/yandex/odyssey :) It's a scalable PgBouncer.
Comment · 8 months ago
I'd love to! But MySQL is developed inside Oracle, and OCA somewhat scares me.
Perhaps, I'll give a try to MariaDB or other forks.
Comment · 1 year ago
And there's also https://postgrespro.com/docs/enterprise/current/multimaster
With a history behind it.
Comment · 2 years ago
I think this should run just fine, why not? As long as you have proper Postgres operator, such proxy will run normally on top of that.
Comment · 2 years ago
+1
there's already well maintained extension https://github.com/fboulnois/pg_uuidv7
It's slightly different from recommendations by draft RFC version (there's no counter), but fully within spec requirements. From practical point there's no difference at all.