From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Mario Ignacio Rodríguez Cortés <ignacio(dot)cortes(at)inegi(dot)org(dot)mx> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pgbouncer |
Date: | 2010-06-03 20:03:47 |
Message-ID: | AANLkTimJM0-5ERpf7pYajPZMverzLA0fiEjWu8au7pcu@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Jun 3, 2010 at 12:40 PM, Mario Ignacio Rodríguez Cortés
<ignacio(dot)cortes(at)inegi(dot)org(dot)mx> wrote:
> hello all:
>
> Well, i have a question if you know about this, i have a webserver in a
> server and i have a database server, the question is: where should I
> install the pgbouncer? in webserver, in database server or is the same?
> whats your experience.
my gut (guess) says here that if the db and web server are on
different boxes, you will want to put pgbouncer on the web server box.
my reasoning is that you have lots of libpq 'auths' going on to
pgbouncer and far fewer real auths to the database, so you want the
leg with the greater # of auths to get the local benefit. reason #2
is the less going on in a dedicated db box the better.
I'm interested in this too...does anyone else have experience in this matter?
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2010-06-03 20:23:07 | Re: Removing CONTEXT from RAISE EXCEPTION messages from triggers |
Previous Message | Marc Bevand | 2010-06-03 19:11:01 | Re: PostgreSQL and NeXpose Rapid 7 Vulnerbility scanning software |