In any case, please check whether upgrading postgresql for you solves the problem. It is possible that mysqldb has/had the same issue.
I am very skeptical this is a web2py issue. So we should try isolate the problem. Massimo On Feb 12, 12:12 am, Anthony <[email protected]> wrote: > On Saturday, February 12, 2011 1:03:48 AM UTC-5, Jonathan Lundell wrote: > > > On Feb 10, 2011, at 6:19 AM, Massimo Di Pierro wrote: > > > > I offer $300 to whoever can identify within 3 weeks and without > > > ambiguity the cause of this problem. The bounty applies even if the > > > problem turns out to be not in web2py but in one of the Python > > > modules, in Apache or in the mod_wsgi implementation. It does not > > > apply if the problem is due to known bug that has already been fixed > > > by the responsible party (for example if you are using an old un- > > > patched python version like 2.5.0 or an old mod_wsgi version). > > > psycopg2 2.0.7 is the version in use in this case. 2.0.8 had this in the > > change log: > > > > * psycopg/pqpath.c (_pq_fetch_tuples): Don't call Python APIs > > > without holding the GIL. > > > Suggestive, no? There's some evidence on the web that this may have led to > > "Segmentation fault - premature end of script headers" errors. > > > 2.3.2 is current > > Though someone reported the same problem with > MySQL:https://groups.google.com/d/msg/web2py/AcCDl5eJnds/AXNyKO6kmBwJ
