Right now the postmaster refuses to start. What is the best way to get
past that to try what you suggest?
[2006-04-06 07:22:50.347 ] 3984 LOG: database system was interrupted
while in recovery at 2006-04-06 02:19:59 Central Daylight Time
[2006-04-06 07:22:50.347 ] 3984 HINT: This probably means that some
data is corrupted and you will have to use the last backup for
recovery.
[2006-04-06 07:22:50.347 ] 3984 LOG: checkpoint record is at
F6/50052F10
[2006-04-06 07:22:50.347 ] 3984 LOG: redo record is at F6/50052F10;
undo record is at 0/0; shutdown FALSE
[2006-04-06 07:22:50.347 ] 3984 LOG: next transaction ID: 313381941;
next OID: 2321597
[2006-04-06 07:22:50.347 ] 3984 LOG: next MultiXactId: 1; next
MultiXactOffset: 0
[2006-04-06 07:22:50.347 ] 3984 LOG: database system was not properly
shut down; automatic recovery in progress
[2006-04-06 07:22:50.347 ] 3984 LOG: redo starts at F6/50052F58
[2006-04-06 07:22:50.347 ] 4076 <bigbird bigbird 127.0.0.1(2236)>
FATAL: the database system is starting up
[2006-04-06 07:22:50.347 ] 4064 <bigbird bigbird 127.0.0.1(2235)>
FATAL: the database system is starting up
[2006-04-06 07:22:50.378 ] 3984 PANIC: heap_clean_redo: no block
-Kevin
>>> On Thu, Apr 6, 2006 at 12:40 pm, in message
<25774.1144345220@sss.pgh.pa.us>,
Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
>> [2006- 04- 06 02:19:57.460 ] 3848 <postgres bigbird 127.0.0.1(3944)>
PANIC: right
> sibling is not next child in "Panel_pkey"
>
> This should be repeatable by re- attempting a VACUUM, right? Please
find
> out which page exactly it's unhappy about (either gdb the crash or
add a
> printout of the "parent" variable to the elog call in nbtpage.c),
then
> pg_filedump the index and look to see what the index contains.
>
> regards, tom lane
