-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 > I'd like to use pgbouncer as connection pooler in our productive > environment, which consists of six master db server plus 6 slaves and many > webserver and services. For example, I'd like to use it as a central point > from where I can redirect client connections easily without changing the > code on application side. > Considering performance issues should I use > pgbouncer on one central VM or put it closer to the db server? It's not clear what your environment is and what 'closer to the db server' means in this context (multiple pgbouncers?), but I would lean towards having a single pgbouncer instance on a central VM, as it means less things to keep track of. There can be advantages to having multiple pgbouncers close to the db, but which is best ultimately depends on your layout, usage pattern, network speeds, etc. - -- Greg Sabino Mullane greg@xxxxxxxxxxxx End Point Corporation http://www.endpoint.com/ PGP Key: 0x14964AC8 201408240939 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAlP5/9EACgkQvJuQZxSWSshKuwCgqALKLyNMPNtzygiibvFEMX4i TTsAoNOcBvvttcGtjewamyc3/HszjoV5 =u8Fk -----END PGP SIGNATURE----- -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
