<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p><span style="font-family:monospace"><span
style="color:#000000;background-color:#ffffff;">Dear pgpool
community</span></span></p>
<p><span style="font-family:monospace">I had the chance to talk to </span><span
style="font-family:monospace"><span
style="color:#000000;background-color:#ffffff;">Muhammad Usama
of Percona back in pgconf.eu 2023 last year in Prague. He told
me that the community is working towards making pgpool better
as far as pooling is concerned. I had kind of extensively
tested 4.4 and was very much happy with the core team's
responsiveness and eagerness to solve problems. Life took me
to other trails in the meantime, but here we are again,
thinking seriously about pgpool once again, as a SQL proxy,
SQL router, and </span>SQL caching solution.</span></p>
<p><span style="font-family:monospace">So, before I get my hands
dirty with 4.5, I'd like to ask if there has been any progress
to the pooling part. Currently we rely on pgbouncer using LDAP
(via PAM) individual connections for users. Using two systems,
pgbouncer in front of the app and pgpool in front of the db,
kind of adds latency so we are exploring all options.</span></p>
<p><span style="font-family:monospace">Thank you!<br>
</span><span style="font-family:monospace"></span></p>
</body>
</html>