#3459: SET TIME ZONE called too often for postgresql_psycopg2 backend ----------------------------------------------+----------------------------- Reporter: Jack Moffitt <[EMAIL PROTECTED]> | Owner: adrian Status: new | Component: Database wrapper Version: SVN | Keywords: Stage: Unreviewed | Has_patch: 1 ----------------------------------------------+----------------------------- Analyzing our database logs I found that 25% of all traffic were calls to SET TIME ZONE. This is currently called for every cursor when using the postgrsql_psycopg2 backend. This only needs to be called when the connection is established. All cursors will get the correct timezone if it is set in the connection. I've attached a patch which calls SET TIME ZONE only on new connections. This eliminates a lot of wasted database traffic and can result in a large performance gain for loaded systems using this backend.
-- Ticket URL: <http://code.djangoproject.com/ticket/3459> Django Code <http://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 post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-updates?hl=en -~----------~----~----~----~------~----~------~--~---
