Tom Lane writes:
> No, there should be ~80 tests in all. I'm not sure why the pg_regress
> script is failing to process the remaining tests when this happens; any
> ideas out there?
It appears that the shell simply aborts on fork failure. Example:
peter ~$ cat test.sh
ulimit -u 30
for i in $(seq 1 25); do
( sleep 5 ) &
echo "all done"
peter ~$ sh test.sh
test.sh: fork: Resource temporarily unavailable
In pg_regress, the big loop is probably done in a subshell, because it's
in a pipe, so the outer script can complete. Detecting failures in
commands in a pipe is of course a bit tricky.
Peter Eisentraut peter_e(at)gmx(dot)net
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2002-10-30 19:43:36|
|Subject: Concerns about statement-timeout patch|
|Previous:||From: Peter Eisentraut||Date: 2002-10-30 19:35:41|