On 2/10/20 9:50 π.μ., Fabio Pardi
wrote:
Hi Rama,yeah reading back some comments over the github on various issues, the pgbouncer hackers were of the philosophy that pgbouncer should remain as query agnostic as possible, in the sense that it should not investigate the content of the queries. Those had to do with classic problems like search_path in transaction mode (some PR's were rejected because of that).
On 02/10/2020 01:42, Rama Krishnan wrote:
Hi Friends,
By using pg bouncer can we split read and queries
pgbouncer is just a connection pooler.
The logic where to send the reads and where the writes, should be in our application.
You might find this interesting : https://github.com/awslabs/pgbouncer-rr-patch
regards,
fabio pardi
-- Achilleas Mantzios IT DEV Lead IT DEPT Dynacom Tankers Mgmt