From: | "Gavin M(dot) Roy" <gmr(at)myyearbook(dot)com> |
---|---|
To: | "phoenix(dot)kiula(at)gmail(dot)com" <phoenix(dot)kiula(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: posgres tunning |
Date: | 2007-08-19 15:26:03 |
Message-ID: | af1bce590708190826m40729745mfa42b88fb6fc0b5d@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
We use PHP, but think of it as a universal PgSQL proxy.. If you connect to
a connection you setup in pgBouncer via psql, it looks like a normal
database. Nothing is different in your code but where you connect (for us,
it's the same as our core DB server on a different server). Let me know if
that answers your question, would be happy to elaborate further if needed.
On 8/19/07, phoenix(dot)kiula(at)gmail(dot)com <phoenix(dot)kiula(at)gmail(dot)com> wrote:
>
> On Jul 23, 5:18 am, g(dot)(dot)(dot)(at)myyearbook(dot)com ("Gavin M. Roy") wrote:
> > You might want to look at pgBouncer to pool your drupal pgsql
> needs. I've
> > found with 2000 needed connections, I can pool out to only 30 backends
> and
> > still push 8k transactions per second.
> >
>
>
>
> How you do use pgBouncer -- through an application developed in PHP or
> Perl? It would be lovely if you can share some info about this
> seemingly useful app which comes with so little documentation on how
> to actually get using. The Skype site mentions the install bits, but
> not how to actually query the pgBouncer stuff instead of the database.
> Very hard to come by some actual code. Could you please share some?
> Many thanks!
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
From | Date | Subject | |
---|---|---|---|
Next Message | Phoenix Kiula | 2007-08-19 15:38:50 | Re: posgres tunning |
Previous Message | Phoenix Kiula | 2007-08-19 14:37:37 | Re: Postgresql performance in production environment |