On Sat, 13 Nov 2004, Gregory S. Williamson wrote: > Looking in the logs I see: > 2004-11-13 13:30:28 LOG: unexpected EOF on client connection > 2004-11-13 13:30:40 LOG: unexpected EOF on client connection > 2004-11-13 13:38:28 LOG: could not send data to client: Broken pipe > 2004-11-13 13:42:15 LOG: server process (PID 30272) was terminated by signal > 9 > 2004-11-13 13:42:16 LOG: terminating any other active server processes > 2004-11-13 13:42:16 WARNING: terminating connection because of crash of > another > server process
> Just to rule out any internal chances, is there any way this shutdown > could have been triggered from within postgres itself ? Can anyone > construct any scenarios in which Linux, postgres or proxool could have > done this without human intervention ? Is it possible that you ran into the out of memory killer? That's the most likely thing beyond admin intervention I can think of. ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
