From: | Bill Moran <wmoran(at)potentialtech(dot)com> |
---|---|
To: | Josh Trutwin <josh(at)trutwins(dot)homeip(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Apache + PHP + Postgres Interaction |
Date: | 2007-08-23 18:55:47 |
Message-ID: | 20070823145547.4ae02a35.wmoran@potentialtech.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
In response to Josh Trutwin <josh(at)trutwins(dot)homeip(dot)net>:
> On Thu, 23 Aug 2007 13:29:46 -0400
> Bill Moran <wmoran(at)potentialtech(dot)com> wrote:
>
> > > Well you haven't given us any indication of data set or what you
> > > are trying to do. However, I can tell you, don't use pconnect,
> > > its broke ;)
> >
> > Broke? How do you figure?
>
> I asked that question earlier this month - this thread has some
> interesting discussion on pconnect:
>
> http://archives.postgresql.org/pgsql-general/2007-08/msg00602.php
Thanks to you and Erik for the link. Not sure how I missed that
thread.
I guess I just feel that "broken" is a bit of a harsh term. If
your expectations are for full-blown connection management from
pconnect(), then you will be disappointed. If you take it for
what it is: persistent connections, then those limitations would
be expected.
*shrug*
I'm just glad there aren't any unknown problems waiting to bite
me ...
--
Bill Moran
http://www.potentialtech.com
From | Date | Subject | |
---|---|---|---|
Next Message | Max Zorloff | 2007-08-23 19:00:32 | Re: Apache + PHP + Postgres Interaction |
Previous Message | Martijn van Oosterhout | 2007-08-23 18:46:06 | Re: "out of memory" error |