Tom Lane wrote:
Oh, that's interesting. The code is barfing on this because/* * Otherwise, we had better assume that the segment is in use. The * only likely case is EIDRM, which implies that the segment has been * IPC_RMID'd but there are still processes attached to it. */ It would seem that maybe your kernel has a different idea of what EIDRM means than we do. You say this persists across a reboot?
I probably should have asked before doing this... but I just rebooted and postgresql came up fine. I hope I didn't screw up the forensics.
So, on the second boot postgresql starts as it should (the first boot being when I powered up after the power outage).
-- -**-*-*---*-*---*-*---*-----*-*-----*---*-*---*-----*-----*-*-----*--- Jon Lapham <[EMAIL PROTECTED]> Rio de Janeiro, Brasil Personal: http://www.jandr.org/ ***-*--*----*-------*------------*--------------------*--------------- ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
