Changes between Initial Version and Version 1 of Ticket #21202, comment 5
- Timestamp:
- Feb 20, 2014, 8:20:13 AM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #21202, comment 5
initial v1 1 Whatever happened to this? Seeing this happen a lot on production with 1.6 . Even worse, the connection then doesn't get closed, and so all future requests error as well. So should we also be closing the bad connection... somewhere?1 Whatever happened to this? Seeing this happen a lot on production with 1.6 and postgres. Even worse, the connection then doesn't get closed, and so all future requests error as well. So should we also be closing the bad connection... somewhere? 2 2 3 3 Longer explanation: As it is with this patch applied (to 1.6, I can't seem to get dev to run), `django.db.close_old_connections()` fails on `conn.rollback()` (which is called by `conn.abort()`) with the same `InterfaceError`. This means that `conn.close_if_unusable_or_obsolete()` never gets called, and the broken connection is reused for later requests, causing all future requests on that connection to error.