#26712: Avoid unnecessary SET TIMEZONE queries on PostgreSQL when no changes are
required
-------------------------------------+-------------------------------------
Reporter: charettes | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database | Version: master
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
The `setting_changed` receiver for the `TIME_ZONE` and `USE_TZ` settings
inconditionally resets each connections timezones on every change even if
not required. This is not an issue for all backends except PostgreSQL
where a query needs to be performed.
Whether or not actions must me performed on `TIME_ZONE` and `USE_TZ`
change should be delegated to the backend specific connection and signal
receivers should only have to clear possibly stale cached values.
--
Ticket URL: <https://code.djangoproject.com/ticket/26712>
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/052.de89dcd3ab17616ea8e6501dd0e52c5a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
