Re: PHP + Postgres: More than 1000 postmasters produce

From: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
To: "Gellert, Andre" <AGellert(at)ElectronicPartner(dot)de>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: PHP + Postgres: More than 1000 postmasters produce
Date: 2004-02-20 17:21:53
Message-ID: Pine.LNX.4.33.0402201019450.10445-100000@css120.ihs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


Have you tested it with regular pg_connects instead of pg_pconnect? while
many people expect pconnects to be faster, often, when they result in the
database having lots of open idle connections, they actually make the
system slower than just using plain connects.

You might want to look into some of the connection pooling options out
there that work with PHP, as persistant connections work well only for a
smaller number of hard working threads, and not so well for a large number
of connections of which only a few are actually hitting the db at the
same time. The becomes especially bad in your situation, where it sounds
like you have multiple databases to connect to, so php is keeping multiple
backends alive for each front end thread.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message tibor 2004-02-20 17:22:36 Re: How can I delete a primary or foreign key?
Previous Message Csaba Nagy 2004-02-20 17:18:21 Re: PHP + Postgres: More than 1000 postmasters produce