From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
---|---|
To: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
Cc: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Failure on tapir / only 10 max connections? |
Date: | 2006-11-11 12:09:00 |
Message-ID: | 3266.24.211.165.134.1163246940.squirrel@www.dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Simon Riggs wrote:
> On Fri, 2006-11-10 at 23:31 -0600, Jim C. Nasby wrote:
>
>> BTW, does make check log it's initdb output anywhere? It'd be handy if
>> it did...
>
> They are logged in src/test/regress/log/initdb.log
> but the make check failure message gives a relative filename, so you
> have to know what the upper part of the path is to find it.
>
> It would be useful to have it say the full path for the failure log, so
> it could be more easily located.
>
But for a buildfarm member this is scarcely necessary - the initdb output
is included in the make check log. See
http://www.pgbuildfarm.org/cgi-bin/show_stage_log.pl?nm=tapir&dt=2006-11-11%20080500&stg=check
and search for 'initdb.log'.
We have had a mechanism for limiting parallelism in make check for quite a
while, and this too is supported by the buildfarm script - just set
MAX_CONNECTIONS in the config. This is pretty much required for Cygwin,
but can also be used for any resource starved machine.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Devrim GUNDUZ | 2006-11-11 15:56:03 | Giving up multiple postmaster + RPM issue |
Previous Message | Richard Huxton | 2006-11-11 11:46:21 | Dumb user question re: updates, Toast, HOT |