#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 tehasdf@…):
The use case for this fix is picking up a new connection after restarting
postgresql (or in my case, pgpool2, but this doesn't seem to matter).
To replicate this error, simply run your app, bring the database down,
send one more request, then bring the database back up. The backend will
start throwing psycopg2.InterfaceError.
To my understanding, both DatabaseError and InterfaceError are reasonable
there, one means you couldn't connect, the other means you couldn't
_re_connect.
FWIW, the fix to this is simply change the line to be `except
(DatabaseError, Database.InterfaceError):`
--
Ticket URL: <https://code.djangoproject.com/ticket/21553#comment:4>
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/067.0d44cbb8eee3c08b754192d59758175d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
