#23325: InterfaceError: connection already closed in PostreSQL
-------------------------------------+-------------------------------------
Reporter: aivus | Owner:
Type: Bug | Status: new
Component: Database layer | Version: 1.6
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: InterfaceError, | Unreviewed
postgresql | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by aivus):
* status: closed => new
* resolution: needsinfo =>
Comment:
Replying to [comment:1 timgraham]:
> Why do you think this is a bug in Django? How do you expect Django to
react when the database terminates the connection?
I think Django should do reconnect, when connection is lost.
I have worker, which work with database(Model.objects.all()) every 2
minutes and I got "connection already closed" error from time to time
Server restart - it's example.
I think this is something like #15802
--
Ticket URL: <https://code.djangoproject.com/ticket/23325#comment:3>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.cb6b38ffc0ef6b20bef4bbacce9c72da%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
