Hi Django developers, At the National Library of Medicine we are doing a lot of Django and AWS. For some of the applications with heavier traffic, we are using RDS Proxy within AWS. RDS Proxy is sort of like a managed version of pgbouncer or pg-pool-II - it must be rather AWS customized because of the way it manages authentication.
Anyway, we found some problems for two reasons: - Our DBAs make the default timezone of the database UTF-8 is AWS CloudFormation to create the databases. - When "ensure_timezone" runs and sets the timezone, that database session is "pinned", so that it will not be shared. Since we already have our own PostgreSQL backend for a couple of other reasons, I just wrote a version of ensure_timezone which fails loudly if the timezone is not UTF-8 rather than set the timezone. I probably should have discussed the issue on this list, and I am remedying this. The failure to manage database connections with RDS Proxy is a pretty severe error, and I am wondering what the community thinks about a connection specific setting about how the timezone should be handled? For lower traffic applications, SET TIMEZONE is fine. For higher traffic applications, raising ImproperlyConfigured is better. Does the group think that a Postgreql specific setting/option should be implemented to prevent session pinning? -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/bf7ac5e1-05e1-4d5b-a2a5-8d1dda04b66bn%40googlegroups.com.
