On Tue, 2003-01-07 at 22:58, Tom Lane wrote:
It also logged that it was killed with signal 9, although I didn't kill it!
Is there something weird going on here?
Is this Linux? The Linux kernel seems to think that killing
randomly-chosen processes with SIGKILL is an appropriate response
Hi guys,
My postgres totally messed up again for some reason (there were like 3
postmasters running, other weirdness).
I noticed this as it was starting up again:
2003-01-07 18:01:34 DEBUG: ReadRecord: unexpected pageaddr 16/F2794000 in
log file 22, segment 249, offset 7946240
2003-01-07
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
My postgres totally messed up again for some reason (there were like 3
postmasters running, other weirdness).
I noticed this as it was starting up again:
2003-01-07 18:01:34 DEBUG: ReadRecord: unexpected pageaddr 16/F2794000 in
log file 22,
It also logged that it was killed with signal 9, although I
didn't kill it!
Is there something weird going on here?
Is this Linux? The Linux kernel seems to think that killing
randomly-chosen processes with SIGKILL is an appropriate response to
running out of memory. I cannot offhand
