Pailloncy Jean-Gerard <[EMAIL PROTECTED]> writes:
> =======================
> 8 of 96 tests failed.
> =======================

The failures all seem to be due to individual tests not getting run:

> ! psql: could not fork new process for connection: Resource temporarily 
> unavailable
> ! psql: could not fork new process for connection: Resource temporarily 
> unavailable
> ! psql: could not fork new process for connection: Resource temporarily 
> unavailable
> ! psql: could not fork new process for connection: Resource temporarily 
> unavailable
> ! psql: could not send startup packet: Broken pipe
> ! psql: could not send startup packet: Broken pipe

(the other two failures are because tables these tests should have
created didn't get created)

The fork failures are easy enough to explain: you have the per-user
process limit set too low.  I suspect the "broken pipe" failures
have the same root cause, but they do seem a bit odd.

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

Reply via email to