2009/5/29 Grzegorz Jaśkiewicz <gryz...@gmail.com>: > On Fri, May 29, 2009 at 2:54 AM, Greg Smith <gsm...@gregsmith.com> wrote: > >> The PostgreSQL connection handler is known to be bad at handling high >> connection loads compared to the popular pooling projects, so you really >> shouldn't throw this problem at it. While kernel problems stack on top of >> that, you really shouldn't start at kernel fixes; nail the really >> fundamental and obvious problem first. > > if it is implemented somewhere else better, shouldn't that make it > obvious that postgresql should solve it internally ? It is really > annoying to hear all the time that you should add additional path of > execution to already complex stack, and rely on more code to handle > something (poolers).
OTOH, you're always free to submit a patch. -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
