Sorry, I guess you can disregard most of my reply:) But a functiont that checks for connections and makes on only if one isn't already there is still good idea, if you are making many queries in a small amount of time. Are you making many queries at once, or the same one many times, or different ones quickly? On Mon, 28 Jan 2002, Chris Ruprecht wrote: > 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 > > > ---------------------------(end of broadcast)--------------------------- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to majordomo@xxxxxxxxxxxxxx) > Chadwick Rolfs - cmr@xxxxxxx Cleveland State University - Student Music Major - The Holden Arboretum Volunteer Computer Programmer - Student Employee --*I finally found powdered water; I just can't figure out what to add to it*--
