re: [lockhart@alumni.caltech.edu: Third call for platform testing] - Mailing list pgsql-hackers

From matthew green
Subject re: [lockhart@alumni.caltech.edu: Third call for platform testing]
Date
Msg-id 14983.986493996@splode.eterna.com.au
Whole thread Raw
In response to Re: [lockhart@alumni.caltech.edu: Third call for platform testing]  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [lockhart@alumni.caltech.edu: Third call for platform testing]  (Tom Ivar Helbekkmo <tih@kpnQwest.no>)
List pgsql-hackers
matthew green <mrg@eterna.com.au> writes:  > digging into the regression.diffs, i can see that:  > - reltime failed
becauseit just had:  > ! psql: Backend startup failed       >    The postmaster log file should have more info, but a
firstthought is  >    that you ran up against process or swap-space limitations.  The parallel  >    check has
fifty-oddprocesses going at its peak, which is more than the  >    default per-user process limit on many Unixen.    >
hmm,maxproc=80 on this system currently and i wasn't really doing anything  > else.  it has 256MB ram and 280MB swap
(unused). exactly what am i looking  > for in the postmaster.log file?  it is 65kb long...    Look for messages about
"forkfailed".  They should give a kernel error  message too.
 


after running `unlimit' (tcsh) before `make check', the only failures i have
are the horology (expected) and the inherit sorted failures, on NetBSD/sparc64.


i also believe the `Bad address' errors were caused when the test was run in
an NFS mounted directory.


.mrg.


pgsql-hackers by date:

Previous
From: steven_vajdic@ivillage.com
Date:
Subject: Re: Re: Integer to float function
Next
From: matthew green
Date:
Subject: re: [lockhart@alumni.caltech.edu: Third call for platform testing]