Appears one of my bigger, but older DB's cored or other this morning and when it came back up the DB shows that it can't start and is possibly corrupted. I've read this was actually due to a kernel bug sometime back (or at least tied to the kernel bug).
I'm wondering if there was any other work arounds or "tricks" that I may try to recover, vs doing a restore from backup?
2014-02-23 03:46:08 PST LOG: aborting startup due to startup process failure
2014-02-23 11:10:09 PST LOG: database system was interrupted while in recovery at 2014-02-23 03:46:04 PST
2014-02-23 11:10:09 PST HINT: This probably means that some data is corrupted and you will have to use the last backup for recovery.
2014-02-23 11:10:09 PST LOG: database system was not properly shut down; automatic recovery in progress
2014-02-23 11:10:09 PST LOG: consistent recovery state reached at 1493/24398AA8
2014-02-23 11:10:09 PST LOG: redo starts at 1493/5306FC8
2014-02-23 11:10:09 PST PANIC: heap_update_redo: invalid lp
2014-02-23 11:10:09 PST CONTEXT: xlog redo hot_update: rel 16399/868691025/959835680; tid 1180404/38; new 1180404/40
2014-02-23 11:10:09 PST LOG: startup process (PID 3175) was terminated by signal 6: Aborted
2014-02-23 11:10:09 PST LOG: aborting startup due to startup process failure
