On Thu, Jul 23, 2009 at 11:36 PM, James Bennett <ubernost...@gmail.com> wrote: > Meanwhile, the codebase stays much simpler and avoids some pitfalls > with potential resource and state leaks.
All pgpool2 does to reset the session to avoid all of these pitfalls is issue "ABORT; RESET ALL; SET SESSION AUTHORIZATION DEFAULT". There's nothing complex about that. (With that added, the TransactionMiddleware change I mentioned earlier isn't needed, either.) I see no need for a complex connection pooling service. You're making this sound much more complicated than it is, resulting in people needing to use configurations much more complicated than necessary. -- Glenn Maynard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
