Odyssey: Scalable PostgreSQL Connection Pooler
1–10 of 54 posts
Re: Odyssey: Scalable PostgreSQL Connection Pooler
#2This looks very cool!
Re: Odyssey: Scalable PostgreSQL Connection Pooler
#3A quick meta BTW, but if you want to keep up with Postgres stuff, we have a newsletter (and covered this Odyssey release earlier today): https://postgresweekly.com/issues/335 (there is RSS, etc.)
Re: Odyssey: Scalable PostgreSQL Connection Pooler
#4Are there benchmarks comparing this to Hikari? What is the benefit to using this over Hikari?
Re: Odyssey: Scalable PostgreSQL Connection Pooler
#5A quick meta BTW, but if you want to keep up with Postgres stuff, we have a newsletter (and covered this Odyssey release earlier today): https://postgresweekly.com/issues/335 (there is RSS, etc.)
Thank you!
Re: Odyssey: Scalable PostgreSQL Connection Pooler
#6Looks cool. Maybe I'm missing something though, but it's not really clear how you'd set this up? Is there a quick start or some examples of configs for different situations?
Re: Odyssey: Scalable PostgreSQL Connection Pooler
#7Are there benchmarks comparing this to Hikari? What is the benefit to using this over Hikari?
This is an external pool, rather than an internal one. That is to say that it runs as a separate process that re-implements the Postgres network protocol to accept incoming connections. The use-case is that it allows you to share one pool across multiple application processes. Depending on your architecture, it can actually make sense to use both an internal pool to reduce connection startup latency and an external pool to reduce your total number of connections.
Re: Odyssey: Scalable PostgreSQL Connection Pooler
#8How does this compare to pgBouncer?
Re: Odyssey: Scalable PostgreSQL Connection Pooler
#9Is this an alternative to PGBouncer, and if so, how do they compare?
Re: Odyssey: Scalable PostgreSQL Connection Pooler
#10Can it do load balancing and failover?