From: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Doubt in pgbouncer |
Date: | 2020-10-02 07:32:26 |
Message-ID: | d06e40f4-f5c8-1a84-d73b-b9da81b14520@matrix.gatewaynet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2/10/20 9:50 π.μ., Fabio Pardi wrote:
> Hi Rama,
>
> 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.
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).
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
From | Date | Subject | |
---|---|---|---|
Next Message | FOUTE K. Jaurès | 2020-10-02 13:19:07 | ERROR: terminating logical replication worker due to timeout |
Previous Message | David G. Johnston | 2020-10-02 07:13:46 | Re: Doubt in pgbouncer |