В логах пишет, объясните что значит?

PANIC: heap_delete_redo: invalid lp
CONTEXT: xlog redo delete: rel 1663/170492837/218105214; tid 74/63
LOG: startup process (PID 11156) was terminated by signal 6: Aborted

Maxim Bogukesteem2010В логах пишет, объясните что значит?

PANIC: heap_delete_redo: invalid lp
CONTEXT: xlog redo delete: rel 1663/170492837/218105214; tid 74/63
LOG: startup process (PID 11156) was terminated by signal 6: Aborted

база побита на уровне файлов. Рекомендация - восстановления базы из backup начисто.
Как вы это смогли получить?

--
Maxim Boguk
www.postgresql-consulting.ru

LOG: database system was interrupted while in recovery at log time 2015-08-19 01:35:07 MSK
HINT: If this has occurred more than once some data might be corrupted and you might need to choose an earlier recovery target.
LOG: entering standby mode
LOG: restored log file "000000010000128C00000017" from archive
LOG: restored log file "000000010000128C00000016" from archive
LOG: redo starts at 128C/16F929E0
LOG: restored log file "000000010000128C00000017" from archive
LOG: restored log file "000000010000128C00000018" from archive
LOG: consistent recovery state reached at 128C/18AB8730
LOG: database system is ready to accept read only connections
LOG: restored log file "000000010000128C00000019" from archive
PANIC: heap_delete_redo: invalid lp
CONTEXT: xlog redo delete: rel 1663/170492837/218105214; tid 74/63
LOG: startup process (PID 11156) was terminated by signal 6: Aborted
LOG: terminating any other active server processes


Полный лог. Основной работает, а этот сервер является репликой и произошел сбой питания более час, ИБП не выдержали.(

Видно отвалился первый примонтированный диск (

LOG: database system was interrupted while in recovery at log time 2015-08-19 01:35:07 MSK
HINT: If this has occurred more than once some data might be corrupted and you might need to choose an earlier recovery target.
LOG: could not open tablespace directory "pg_tblspc/1784050/PG_9.0_201008051": Нет такого файла или каталога
LOG: entering standby mode
LOG: redo starts at 128C/16F929E0
FATAL: could not create directory "pg_tblspc/1784050/PG_9.0_201008051": Отказано в доступе
CONTEXT: xlog redo vacuum: rel 1784050/1784616/218441046; blk 340, lastBlockVacuumed 339
LOG: startup process (PID 1930) exited with exit code 1
LOG: terminating any other active server processes
LOG: database system was interrupted while in recovery at log time 2015-08-19 01:35:07 MSK
HINT: If this has occurred more than once some data might be corrupted and you might need to choose an earlier recovery target.
LOG: entering standby mode
LOG: redo starts at 128C/16F929E0
LOG: consistent recovery state reached at 128C/18AB8660
LOG: invalid record length at 128C/18AB8660
LOG: database system is ready to accept read only connections
LOG: streaming replication successfully connected to primary
LOG: invalid record length at 128C/18AB8660
FATAL: terminating walreceiver process due to administrator command
LOG: invalid record length at 128C/18AB8660
LOG: invalid record length at 128C/18AB8660
LOG: invalid record length at 128C/18AB8660
LOG: invalid record length at 128C/18AB8660
LOG: invalid record length at 128C/18AB8660
LOG: invalid record length at 128C/18AB8660
LOG: invalid record length at 128C/18AB8660

Так понимаю без вариантов восстанавливать реплику с нуля( ???