On Sat, Oct 15, 2011 at 07:44:29PM +0200, Christoph Berg wrote:
> > > > I still don't see how this could be a php5-pgsql bug since it's caused
> > > > by pgsql version.
> > >
> > > I filed it preemptively on all so as to solicit help... if there is no odd
> > > variable behavior in php5-pgsql based on server version, please feel free
> > > to
> > > reassign away.
> > >
> > > > But still I have one more another important question:
> > > >
> > > > Is this related to libpq5 version or postgresql server version?
> > >
> > > I did not test downgrading libpq5, just postgresql-*, good point, that'll
> > > be my next step. After vacation...
> >
> > I couldn't resist, and it seemed like an easy test. I manually downgraded
> > libpq5 to 8.4.7-0squeeze2, restarted both PostgreSQL and Apache (mod_php),
> > and the test result was the same.
>
> Hi Joy,
>
> I doubt that this is a postgresql server bug (no one else has hit it
> yet). As the server never closes connections by itself, it must be on
> the client side, either in libpq5 (which I doubt), or (more likely) in
> some connection caching layer which you mentioned earlier. Did you
> also upgrade apache and/or moved to some other MPM? What about
> mod_php?
I didn't change the MPM but I did upgrade the entire web server, from lenny
to squeeze, as I said in the first mail :) so yes, the underlying Apache
and mod_php were upgraded the same way as well.
In retrospect, it's almost as if it was actually a failure in lenny's
software to observe the persist option, and squeeze actually does the
persistence (and I don't actually want it because it kills the use case).
--
2. That which causes joy or happiness.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
