From: | Gabriele Lohss <gabriele(dot)lohss(at)gmail(dot)com> |
---|---|
To: | Greg Sabino Mullane <greg(at)turnstep(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pgbouncer setup in the architecture |
Date: | 2014-08-27 09:03:36 |
Message-ID: | CANo3p7_cgKszcAd1EDFa1nYsizVSBj60MxUhG6ghM3VTWhLamQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
thanks, you're right. My description wasn't very concrete. Our current set
up is a single pgbouncer instance running on a VM in the same network like
the webapplications. The database servers are in another firewall protected
network. So the pgbouncer is now running on a standalone VM. I was
wondering if this setup is a propper solution, but I guess we still have to
test the perfomance.
Until now I always installed pgbouncer on a already existing database
server and the basic configuration was quite easy. When running on a
central VM separate to the database its is connecting too, is it necessary
to have a running postgresql instance on this VM too? I want to connect to
the pgbouncer database as well, but therefor I need a postgresql database
server, right? Or do I just need the client packages?
Thanks for the help,
Gaby
2014-08-24 17:09 GMT+02:00 Greg Sabino Mullane <greg(at)turnstep(dot)com>:
>
> -----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(at)turnstep(dot)com
> 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-----
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ramesh T | 2014-08-27 09:52:18 | Deletion |
Previous Message | Arze, Cesar | 2014-08-27 03:18:22 | Re: Postgres 9.1 issues running data directory from VMware shared folder |