Re: Possible fix for occasional failures on castoroides etc
От | Dave Page |
---|---|
Тема | Re: Possible fix for occasional failures on castoroides etc |
Дата | |
Msg-id | CA+OCxoywEsXE=QiR_J8+hOjiFLhROxc19xMquu44SyPp14so2Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Possible fix for occasional failures on castoroides etc (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: Possible fix for occasional failures on castoroides etc
|
Список | pgsql-hackers |
On Sun, Sep 16, 2012 at 12:44 PM, Andrew Dunstan <andrew@dunslane.net> wrote: > > On 09/16/2012 12:04 PM, Tom Lane wrote: >> >> It's annoying that the buildfarm animals running on older versions of >> Solaris randomly fail with "Connection refused" errors, such as in >> today's example: >> >> http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=castoroides&dt=2012-09-15%2015%3A42%3A52 >> >> I believe what's probably happening there is that the kernel has a small >> hard-wired limit on the length of the postmaster's accept queue, and you >> get this failure if too many connection attempts arrive faster than the >> postmaster can service them. If that theory is correct, we could >> probably prevent these failures by reducing the number of tests run in >> parallel, which could be done by adding say >> MAX_CONNECTIONS=5 >> to the environment in which the regression tests run. I'm not sure >> though if that's "build_env" or some other setting for the buildfarm >> script --- Andrew? >> >> > > > > Yes, in the build_env section of the config file. > > It's in the distributed sample config file, commented out. I've added MAX_CONNECTIONS=5 to both Castoroides and Protosciurus. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: