On 7/3/24 23:32, Scott Ribe wrote:
the read only detection is tricky--consider transaction level pooling, and the first query is read only
Hello
pgpool does a great job at that. pgpool does load balancing to the first
statement that is considered a write statement, for that point on, the
rest of the transaction is routed to the primary.
But the question here is how to achieve all of the aforementioned
features, of all those great tools combined, or ideally combined in one.
--
Scott Ribe
scott_ribe@xxxxxxxxxxxxxxxx
https://www.linkedin.com/in/scottribe/
On Jul 3, 2024, at 2:25 PM, Achilleas Mantzios <a.mantzios@xxxxxxxxxxxxxxxxxxxx> wrote:
Dear Members
I am searching (like many others) of the holy grail of PostgreSQL pooling + Load Balancing . Ideally I would like :
- A pgbouncer with better/native LDAP (not PAM) / and eventually Kerberos support
- A pgbouncer enhanced with load balancing read-only queries (like pgpool)
or
- A pgpool-II with better resources utilization / more efficient pooling (like pgbouncer)
There are other solutions available pgcat (no LDAP), odyssey (no load balancing) , pgagroal, supavisor, none of which seem to cover the above.
Some ppl advice , keeping pgbouncer close to the app(s) and pgpool close to the DB. But kinda had mixed feelings putting the two work together.
I'd like to ask if there any thoughts or even hopes that some of the above will be available in a single software, or otherwise how do people tackle this.
Thank you
--
Achilleas Mantzios
IT DEV - HEAD
IT DEPT
Dynacom Tankers Mgmt (as agents only)
