Received: from tomts20-srv.bellnexxia.net (tomts20.bellnexxia.net [209.226.175.74]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0VLkPl03334 for ; Thu, 31 Jan 2002 16:46:25 -0500 (EST) (envelope-from fbax@sympatico.ca) Received: from ACER ([65.94.209.155]) by tomts20-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with SMTP id <20020131214625.QCYQ9253.tomts20-srv.bellnexxia.net@ACER>; Thu, 31 Jan 2002 16:46:25 -0500 Message-Id: <3.0.6.32.20020131162954.01a3f100@pop6.sympatico.ca> X-Sender: b1wudu74@pop6.sympatico.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Thu, 31 Jan 2002 16:29:54 -0500 To: Marco Colombo From: Frank Bax Subject: Re: pg_pconnect - ?? Cc: Chris Ruprecht , PostGreSQL PHP Group In-Reply-To: References: <3.0.6.32.20020128141957.02130660@pop6.sympatico.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Archive-Number: 200201/99 X-Sequence-Number: 902 At 09:09 PM 1/31/02 +0100, Marco Colombo wrote: >On Mon, 28 Jan 2002, Frank Bax wrote: > >> The connection will only be reused if the *same* apache child process >> handles the request. You should expect to see many postgres client >> connections. >> A) Each database/user connection combination. >> B) Each apache child process >> >> Multiply A*B to get max number of concurrent connections. If A*B can go >> over postgres connection limit, then you might start getting connection >> refused messages. > >pgsql.max_persistent integer > The maximum number of persistent Postgres connections per process. > ^^^^^^^^^^^ > >you can have more than one persistent connection per httpd process. Now >that I think about it, it seems a good idea to limit it to some sane >value. I was actually referring to max_connections in postgresql.conf (as the limit for A*B). I expect that pgsql.max_persistent puts a limit on A rather than A*B. I let this run wild (value=-1) on my system and use default of max_connections=64) in postgresql. Frank