Re: [Pgbuildfarm-members] guppie: 64MB RAM too small?

Jim C. Nasby said:
> On Tue, Mar 21, 2006 at 06:39:58AM -0600, Andrew Dunstan wrote:
>> There seems to be some confusion here. The MAX_CONNECTIONS setting for
>> "make check" is a limit on the parallelism of the test. It's a gadget
>> we put in a couple of years ago to allow cygwin to run "make check" as
>> it couldn't run 20 concurrent connections. It is not connected to the
>> server setting that is indeed set up by initdb. Buildfarm very
>> deliberately always runs with the default settings that initdb sets
>> up.
>
> Ok, so the problem was just that the database ran out of connections
> because initdb had to set max_connections really low. Thanks for
> clarifying.
>
> It's probably worth adding a note about this somewhere in
> http://pgfoundry.org/docman/view.php/1000040/4/PGBuildFarm-HOWTO.txt --
>

No, let's start again.

The user's machine ran out of resources. That can't be because inbitdb set
max_connections too low - if anything it has probably set them too high. I
suggested that he could possibly limit resource use by limiting the number
of concurrent connections "make check" would use, by using the *UNRELATED*
MAX_CONNECTIONS=n make flag. This flag is not part of buildfarm - it
predates buildfarm in fact. It's part of the postgres build system - look in
pg_regress.sh and the associated make file. Buildfarm has support for it as
shown in the sample config file.

cheers

andrew