#13215: Random OperationalError when using FastCGI prefork + PostgreSQL
-------------------------------------+--------------------------------------
Reporter: hcarvalhoalves | Owner: nobody
Status: new | Milestone:
Component: Core framework | Version: 1.1
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Comment (by hcarvalhoalves):
''- Does it matter what the view is doing?''
The shown traceback triggers the bug in admin code, but I have the same
behaviour in middleware code, before any view is processed. So, no.
''- Does it happen consistently on the same view?''
It will happen randomly, and for any view/pre-view code that tries to
access the database. But it always in the first code trying hit the DB.
''- Does it occur under certain load conditions?''
No, this doesn't seem to affect. You can get the same behaviour in a local
server.
''- Does it only occur on long-lived connections?''
I have it happening randomly and regardless of my keep-alive
configuration, request timeout or view processing time.
''- Is the stack trace always the same? If it isn't, what is the common
element?''
Always caused in the first code trying hit the DB. This might indicate
that the DB cursor is dead from request start.
----
In some way, this bug is similar to #9437
--
Ticket URL: <http://code.djangoproject.com/ticket/13215#comment:2>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
