| From: | Chris Ruprecht <chrup999(at)yahoo(dot)com> |
|---|---|
| To: | "PostGreSQL PHP Group" <pgsql-php(at)postgresql(dot)org> |
| Subject: | Re: pg_pconnect - ?? |
| Date: | 2002-01-28 20:31:01 |
| Message-ID: | p05101218b87b6220cfa3@[192.168.0.6] |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-php |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chadwick Rolfs | 2002-01-28 20:50:54 | Re: pg_pconnect - ?? |
| Previous Message | Mitch Vincent | 2002-01-28 19:56:59 | Re: pg_pconnect - ?? |