On Thu, Feb 28, 2013 at 4:10 PM, Christophe Pettus <x...@thebuild.com> wrote:
> > On Feb 28, 2013, at 11:09 AM, David Cramer wrote: > > > Immediately for anyone who has configured more workers than they have > Postgres connections (which I can only imagine is common among people who > havent setup infrastructure like pgbouncer) things will start blowing up. > > If they have this configuration, it's an error. The fact that the error > is now surfacing doesn't make it a correct configuration. Why is this an error? It sounds more like a barrier to entry to me. Most sites won't ever hit the maximum number of database connections, but they over provision in their app (or they add more apps to the database as they see their database load isn't so high). Seems to me if we enable this by default, we are requiring a certain set of hardware that is way more demanding than the actual use case for the app, just for a small speed increase. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
