PANIC: heap_update_redo: invalid lp

From: Chavdar Kopoev <chavdar(at)kopoev(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: PANIC: heap_update_redo: invalid lp
Date: 2011-02-07 18:54:55
Message-ID: 4D503FFF.3080704@kopoev.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hello,

My production database cannot start:
* Starting PostgreSQL 8.4 database server
* The PostgreSQL server failed to start. Please check the log output.

Log file as follow:
2011-02-07 19:39:52 EET 891LOG: database system was interrupted while
in recovery at 2011-02-07 19:33:25 EET
2011-02-07 19:39:52 EET 891HINT: This probably means that some data
is corrupted and you will have to use the last backup for recovery.
2011-02-07 19:39:52 EET 891LOG: database system was not properly shut
down; automatic recovery in progress
2011-02-07 19:39:52 EET 891LOG: redo starts at 88/37705758
2011-02-07 19:39:52 EET [unknown] [unknown][local] 892LOG: incomplete
startup packet
2011-02-07 19:39:52 EET 891PANIC: heap_update_redo: invalid lp
2011-02-07 19:39:52 EET 891CONTEXT: xlog redo hot_update: rel
1663/16388/16677; tid 562/9; new 562/10
2011-02-07 19:39:52 EET 889LOG: startup process (PID 891) was
terminated by signal 6: Aborted
2011-02-07 19:39:52 EET 889LOG: aborting startup due to startup
process failure

My target are a few tables from the database to be restored. Other
information is not critical, can be restored from recent backup.
Any help with restoring the database will be very much appreciated.

Regards,
Chavdar Kopoev

Browse pgsql-admin by date

  From Date Subject
Next Message Antonio Biondo 2011-02-08 09:27:47 Re: maximum rows to retrive
Previous Message Kevin Grittner 2011-02-07 18:14:36 Re: How to