Thanks. Indeed pgBouncer is the usual candidate in front of postgres streaming
replication, together with pgpool. Take care that your link on pgBouncer dates
back from 2008 !.
I had a look at pgBouncer in the past, but it was not actively maintained at
that time. So I settled on a combination of pgpool and repmgr. People on pgpool
mailing list are very reactive and helpful and the doc on the project is
On Wednesday, February 14, 2018, 8:44:47 PM GMT+1, Melvin Davidson
On Wed, Feb 14, 2018 at 2:27 PM, Pierre Timmermans <ptim...@yahoo.com> wrote:
pgpool does just that: it enables you to use the standby database as a read
only while other queries are sent to the primary database only
(http://www.pgpool.net/). Good product and good support (on the list°
This looks a very interesting possibility, although it is more related to
automated failover than to load balancing of read only queries :
http://paquier.xyz/ postgresql-2/postgres-10- libpq-read-write/, depending on
your client it might be supported. It is not supported - yet ? - by the
On Wednesday, February 14, 2018, 3:29:03 PM GMT+1, Venkateswaran
I am also trying to split read and write queries, where reads should go to
the slave server (streaming replication) and writes to the master server.
Any tool available to perform this activity instead of two connection pool?
Sent from: http://www.postgresql-archive. org/PostgreSQL-general- f1843780.html
Actually, if you are looking for load balancing PgBouncer is better than
PgPool. There is a nice article about that.
I used PgBouncer in a few of ny previous positions and found it to be very fast
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.