Received: from smtp011.mail.yahoo.com (smtp011.mail.yahoo.com [216.136.173.31]) by postgresql.org (8.11.3/8.11.4) with SMTP id g0SKV6l31543 for ; Mon, 28 Jan 2002 15:31:06 -0500 (EST) (envelope-from chrup999@yahoo.com) Received: from chill-025.dfw.tx.bbnow.net (HELO ?192.168.0.6?) (24.219.2.25) by smtp.mail.vip.sc5.yahoo.com with SMTP; 28 Jan 2002 20:31:07 -0000 Mime-Version: 1.0 X-Sender: chrup999@pop.mail.yahoo.com Message-Id: In-Reply-To: <009a01c1a835$f2d76520$0200000a@Mitch> References: <3.0.6.32.20020128141957.02130660@pop6.sympatico.ca> <009a01c1a835$f2d76520$0200000a@Mitch> Date: Mon, 28 Jan 2002 14:31:01 -0600 To: "PostGreSQL PHP Group" From: Chris Ruprecht Subject: Re: pg_pconnect - ?? Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by postgresql.org id g0SKi1m38188 X-Archive-Number: 200201/78 X-Sequence-Number: 882 Ok, so from what I see on here, pg_pconnect doesn't have any advantages over pg_connect in my situation. I have the web server running on the same machine as the database server and yes, I have allocated 16384 shared buffers (at 8 KB each, this is 128 MB of shared memory). I have not noticed any connect overhead when opening a web page which connects to the database (99% of them do), the connection is instantaneously, so I guess, I don't need to do anything here. I was under the impression, that a persistent connection would open one and only one process which then will be used all the time without creating more child processes which keep lingering about. I guess, I was wrong here ... Best regards, Chris -- Chris Ruprecht Network grunt and bit pusher extraordinaíre _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com