On Fri, Jul 24, 2009 at 9:20 PM, James Bennett<ubernost...@gmail.com> wrote: > Suppose we start with a patch which does the sort of thing you > apparently want: hold on to the connection, and reset it after each > request/response cycle. That patch would never get committed, because > it would have even worse side effects (see: "spinning up a server > process ties up a DB handle for as long as the process lives?") and > could quite realistically cause resource starvation.
8-16 connections from the 8-16 backend threads I'm starting are going to swamp Postgresql? Sorry, no. -- 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 -~----------~----~----~----~------~----~------~--~---
