Just use https://github.com/yandex/odyssey :) It's a scalable PgBouncer.
yandex is a russian company, so no, don't use it
[dead]
We scaled PgBouncer to 4x throughput
41–50 of 67 posts
Re: We scaled PgBouncer to 4x throughput
#42PgBouncer is a great piece of software. We use that heavily and had made us DB operations pretty easy
Re: We scaled PgBouncer to 4x throughput
#43Re: We scaled PgBouncer to 4x throughput
#44Earlier quoted context omitted.
Do you boycott American companies too? I'm assuming you boycott Russian companies because Russia causes death and destruction. But the USA caused much more death and destruction than Russia ever did - do you boycott them too?
[flagged]
Believe what you do, it's more useful for war-mongering nation states when you see things in so black and white manner.
Re: We scaled PgBouncer to 4x throughput
#45Earlier quoted context omitted.
Do you boycott American companies too? I'm assuming you boycott Russian companies because Russia causes death and destruction. But the USA caused much more death and destruction than Russia ever did - do you boycott them too?
[flagged]
But in this case you would be supporting one of the good things (science & technology) they've done, right? A database connection pooler is not necessarily military technology.
Re: We scaled PgBouncer to 4x throughput
#46Why does PgBouncer need to care about cancellation requests at all? Why can't it just forward the cancellation to postgres, which then responds to the cancelled query with an error instead of a response, and then the bouncer for that connection handles that error?
Re: We scaled PgBouncer to 4x throughput
#47Just use https://github.com/yandex/odyssey :) It's a scalable PgBouncer.
We started with the most battle-tested and native option to Postgres, which is PgBouncer and tried tuning it the right way. Also now that long due kinks like support for prepared statements are solved, it’s been working really well. There are many customers scaling well with 10K+ Postgres connections. We will consider other options like odyssey, pgdog in the future! Side note: I’m not a big fan of having 10K+ connect…
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.
Re: We scaled PgBouncer to 4x throughput
#48Why does PgBouncer need to care about cancellation requests at all? Why can't it just forward the cancellation to postgres, which then responds to the cancelled query with an error instead of a response, and then the bouncer for that connection handles that error?
Query cancels are out of band from the query connection so PGBouncer has to land it on the right server and the right connection. So PGBouncer serves a bogus-but-tracked cancel PID+secret to the client, which then goes to PGBouncer and PGBouncer figures out the right server/process to send the actual PID+secret to. PGBouncer also has to make sure that the connection/PID is still actually running the query; strictly speaking, a client can believe a query is still running when PGBouncer knows it's already complete and the connection has been reused.
Re: We scaled PgBouncer to 4x throughput
#49Earlier quoted context omitted.
nginx is also Russian, so don't use... a third of the web.
nginx was built by one person. I'm talking about a russian corporation that has (inescapable) ties to kremlin
Yandex actually split up because of disagreement with the Russian governement and the war.
Check out Nebius
Re: We scaled PgBouncer to 4x throughput
#50Earlier quoted context omitted.
[flagged]
Objectively speaking, Russia is one of the most creative and innovative societies of all time. Literature, science, music, sporting, mathematics, computing, you name it, a Russian has innovated in it.
What would be some of these innovations and contributions in the last 20 years?