#23830: Make expired session clearing on database backend scale better
-------------------------------------+-------------------------------------
Reporter: adamchainz | Owner:
Type: | adamchainz
Cleanup/optimization | Status: assigned
Component: contrib.sessions | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage:
Has patch: 1 | Unreviewed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 1 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by iljamaas):
Giving the patch a second thought, it breaks possible signal handlers
POST_DELETE and PRE_DELETE as they are not triggered in this way.
''The same problem is with my own proposal above.''
So I think your patch is not a solution.
On the other hand, how does it happen that there are so many expired
sessions to remove. Can't you just run the session cleanup more often?
--
Ticket URL: <https://code.djangoproject.com/ticket/23830#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/068.ba773a6c5791dc3b888147f1cfccfb95%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.