#21553: InterfaceError in Postgres
-------------------------------------+-------------------------------------
Reporter: anonymous | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer | Version: 1.6
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by KyleMac):
I just ran into this as well.
For some reason postmaster killed a process and so all of postgres
restarted to avoid corruption. Postgres was down for only a few seconds
and normal service should have resumed.
However, all the persistent db connections in Django were now dead and
needed to reconnect. But is_usable was throwing "InterfaceError:
connection already closed" and so Django would never reconnect and only
served error 500 pages until I manually restarted it.
--
Ticket URL: <https://code.djangoproject.com/ticket/21553#comment:6>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.50c1978cd29783bda4cca0deea799101%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
