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
t
On 19/08/07, Gavin M. Roy <[EMAIL PROTECTED]> wrote:
> 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
On Jul 23, 5:18 am, [EMAIL PROTECTED] ("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 a
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.
On 7/21/07, Arnaldo Gandol <[EMAIL PROTECTED]> wrote:
I have a drupal site working with postgres that do
On Sat, Jul 21, 2007 at 09:54:35PM -0500, Arnaldo Gandol wrote:
> I have a drupal site working with postgres that does not tolerate more
> than 200 concurrent connections(it is not hardware fault).
What does "not tolerate" mean? Does the database refuse connections
beyond 200? Does it permit co
I have a drupal site working with postgres that does not tolerate more
than 200 concurrent connections(it is not hardware fault). Does anybody know
how to adjust postgres parameters and what are them?, or how to get a better
performance in any way?
