From: | Christian Mair <chris(at)1006(dot)org> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | jnasby(at)pervasive(dot)com, pgbuildfarm-members(at)pgfoundry(dot)org |
Subject: | Re: [Pgbuildfarm-members] guppie: 64MB RAM too small? |
Date: | 2006-03-21 13:20:09 |
Message-ID: | 1142947209.3709.47.camel@dell.home.lan |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | buildfarm-members pgsql-hackers |
> 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.
Yes,
Neither PostgreSQL nor the buildfarm code is to blame.
The problem was OpenBSD's restrictive default limit of max 64
user processes. I raised that on OpenBSD's side and as you can see
guppie turned green :)
Bye, Chris.
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2006-03-21 14:19:15 | Re: [Pgbuildfarm-members] guppie: 64MB RAM too small? |
Previous Message | Andrew Dunstan | 2006-03-21 13:01:58 | Re: [Pgbuildfarm-members] guppie: 64MB RAM too small? |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-03-21 13:49:18 | Re: [GENERAL] A real currency type |
Previous Message | Andrew Dunstan | 2006-03-21 13:01:58 | Re: [Pgbuildfarm-members] guppie: 64MB RAM too small? |