Re: Problems with max_connections parameter

Hi Tom

The test program is running in other 5 client machines.
In the logs of my test program, the max_connection parameter limit is never
reached.

Regards
Jorge

On Mon, Dec 6, 2010 at 1:31 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Jorge Augusto Meira <jmeira@c3sl.ufpr.br> writes:
> > The error message was:
> > "Erro Conex=E3o: A tentativa de conex=E3o falhou."
> > or
> > "Erro Conex=E3o: FATAL: connection limit exceeded for non-superusers"
>
> Hmm ... I can't find the first of those anywhere in the 8.4 message
> lists; but the second one definitely says that you *are* hitting the
> max_connections limit, whether you think you should be or not.
>
> I wonder whether you are neglecting to allow for the fact that backends
> have a nonzero shutdown time?  If you disconnect and immediately
> reconnect, it's possible that your old backend is still around, so that
> the new connection attempt causes max_connections to be exceeded.  This
> is particularly likely if the test program is on the same machine as the
> database server, because the test program itself is likely to have a
> higher scheduling priority than the old backend.
>
>                        regards, tom lane
>