On Tue, Aug 16, 2011 at 12:52 AM, Chris Travers <chris.travers@xxxxxxxxx> wrote: > On Mon, Aug 15, 2011 at 10:05 PM, Scott Marlowe <scott.marlowe@xxxxxxxxx> wrote: > >> >> Yep. Also, it's REAL easy to stick a caching layer like memcached >> into the middle tier app layer, but nearly impossible to do so in >> pgsql. For large systems, this would make pg as an app server a nogo. >> But for small to medium sized systems that don't need caching it >> could work out. >> > The other big scalability limitation for Pg as an app server is you > really can't do connection pooling. why not? if you are serving http, just put thin connection pooler in your http server (node.js would be great for that). if you are serving libpq directly, you can pool with pgbouncer. merlin -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
