Opened 12 years ago
Last modified 9 years ago
#19948 new Cleanup/optimization
Improve connection reset under PostgreSQL
| Reported by: | Aymeric Augustin | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
On django-developers, Christophe Pettus says:
It would be helpful to have a backend method that performers the "restore connection between uses" function, rather than just use connection.abort() (of course, the default implementation can use that). For example, on PostgreSQL, ABORT; DISCARD ALL is the recommended way of resetting a connection, so being able to implement that would be great.
This was independently suggested by Anssi, and it looks like a good idea to implement.
Note:
See TracTickets
for help on using tickets.
I think "ABORT; DISCARD ALL" may also need to be followed up with
self.init_connection_state(), because it would otherwise discard the session state that Django sets up for each connection.