Is there any way to work around this problem? We no longer have support for
this machine, so will probably not be able to recompile the kernel. Strange
too, that it didn't happen on earlier versions.
Regards,
- Steve Nunez
On 4/3/02 10:15, "Tom Lane" <[EMAIL PROTECTED]> wrote:
> Steven N=?ISO-8859-1?B?+vE=?=ez <[EMAIL PROTECTED]> writes:
>> This time I've included the log file...
>
>> DEBUG: connection startup failed (fork failure): Resource temporarily
>> unavailable
>> DEBUG: connection startup failed (fork failure): Resource temporarily
>> unavailable
>> DEBUG: connection startup failed (fork failure): Resource temporarily
>> unavailable
>> DEBUG: connection startup failed (fork failure): Resource temporarily
>> unavailable
>> DEBUG: connection startup failed (fork failure): Resource temporarily
>> unavailable
>> DEBUG: connection startup failed (fork failure): Resource temporarily
>> unavailable
>
> At a guess, you have the max-processes-per-user limit set too low.
>
> The postmaster attempts to report the fork failure to the client,
> but it looks like (at least on your platform) libpq gives up before
> receiving the error message. I wonder if it'd make sense for libpq
> to ignore send failure on the startup packet, so it could move ahead
> to receive the error message. I have a feeling that would make the
> behavior worse in other scenarios, though, so it may not be a win.
>
> regards, tom lane
>
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
