| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | pgbuildfarm-members(at)pgfoundry(dot)org |
| Subject: | Re: [Pgbuildfarm-members] guppie: 64MB RAM too small? |
| Date: | 2006-03-21 12:25:41 |
| Message-ID: | 20060321122540.GV15742@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | buildfarm-members pgsql-hackers |
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
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2006-03-21 12:39:58 | Re: [Pgbuildfarm-members] guppie: 64MB RAM too small? |
| Previous Message | Jim C. Nasby | 2006-03-21 09:44:06 | Re: [Pgbuildfarm-members] guppie: 64MB RAM too small? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2006-03-21 12:39:58 | Re: [Pgbuildfarm-members] guppie: 64MB RAM too small? |
| Previous Message | Bruce Momjian | 2006-03-21 12:17:58 | Re: SQL/XML extension |