Re: Problems with max_connections parameter
От | Tom Lane |
---|---|
Тема | Re: Problems with max_connections parameter |
Дата | |
Msg-id | 26309.1291649487@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Problems with max_connections parameter (Jorge Augusto Meira <jmeira@c3sl.ufpr.br>) |
Ответы |
Re: Problems with max_connections parameter
Re: Problems with max_connections parameter |
Список | pgsql-bugs |
Jorge Augusto Meira <jmeira@c3sl.ufpr.br> writes: > The error message was: > "Erro Conexão: A tentativa de conexão falhou." > or > "Erro Conexão: 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
В списке pgsql-bugs по дате отправления: