#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
-------------------------------------+-------------------------------------
Changes (by adam-iris):
* status: closed => new
* resolution: needsinfo =>
Comment:
We are getting this error when the connection has been closed by Postgres:
{{{
InterfaceError: connection already closed
}}}
There was an earlier ticket (#15802) about this error in particular; from
looking at the code, it seems that the fix for the earlier ticket involved
catching {{{ Database.Error}}} in {{{ close() }}} but in our case it looks
like the error is being raised from {{{ is_usable()}}} which only catches
{{{Database.DatabaseError}}}.
I would argue that {{{is_usable()}}} should never throw; regardless of
what error occurs, the result is that the database is not usable.
--
Ticket URL: <https://code.djangoproject.com/ticket/21553#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/067.9cc456fcf7a92f266803b4df7e1fa37d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
