On Wed, May 28, 2003 at 19:18:45 -0400,
Andy Kriger <akriger@greaterthanone.com> wrote:
> The default config for max_connections is 32.
>
> We have a server where we host web applications, each with its own
> connection pool. For every additional webapp, I'm supposing that we are
> placing more and more demands on those 32 connections (dividing a fixed
> resource among increased clients).
>
> So, it would seem to make sense to increase the max_connections whenever a
> new webapp is created. However, what is the drawback to having more
> connections available? Is it memory? disk space? file handles? Is there a
> practical limit?
It shouldn't be based on the web apps as much as what the web server
needs. For example if you run apache using the prefork mpm, you will
want to make the number of allowed postgres connections greater than
the number of allowed apache processes.