[Catalog-sig] psycoph errors from pypi

Phillip J. Eby pje at telecommunity.com
Fri Jul 6 19:21:00 CEST 2007

At 08:04 AM 7/6/2007 -0400, Jim Fulton wrote:
>On Jul 5, 2007, at 10:33 PM, Martin v. Löwis wrote:
> > I now do, somewhat. Apparently, when you discard a cursor object
> > in psycopg, and create a new one, that doesn't necessarily start
> > a new transaction. So if there was some SQL error in the connection,
> > it stops accepting further SQL statements.
> >
> > I fixed that by rolling back the connection after each request,
> > and before each new request.
> >
> > What I don't understand is why there was an error in the first
> > place (or what that error was).
>OK, this probably isn't helpful, but I can't help asking an obvious
>question.  Did something change in the software other than a switch
>from mod_python to FastCGI?

That wouldn't be necessary for this to become a problem.  If PyPI was 
CGI before, then any sort of transient SQL problem wouldn't have had 
this effect, because the DB connection would've been closed at the 
end of each request.  So, it's probably an existing SQL error in PyPI.

More information about the Catalog-SIG mailing list