Avoid unnecessary SET TIMEZONE queries on PostgreSQL when no changes are required
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.
Change History
(6)
| Has patch: |
set
|
| Needs documentation: |
set
|
| Triage Stage: |
Unreviewed → Accepted
|
| Needs documentation: |
unset
|
| Needs tests: |
unset
|
| Triage Stage: |
Accepted → Ready for checkin
|
| Resolution: |
→ fixed
|
| Status: |
new → closed
|
PR