#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 |
-------------------------------------+--------------------------------------
Changes (by russellm):
* needs_better_patch: => 0
* stage: Unreviewed => Accepted
* needs_tests: => 0
* needs_docs: => 0
Comment:
I'll accept this, but I wouldn't hold my breath on getting a solution
unless you can narrow down the cause of the problem. Does it matter what
the view is doing? Does it happen consistently on the same view? Does it
only occur under certain load conditions (CPU, memory, or HTTP access
load)? Does it only occur on long-lived connections? Is the stack trace
always the same? If it isn't, what is the common element?
In short, we need *anything* that can make this less random, and more
repeatable.
--
Ticket URL: <http://code.djangoproject.com/ticket/13215#comment:1>
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 django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
