Re: PANIC: right sibling 2019 of block 2018 is not next child of 1937 in index "sl_log_2_idx1"

Jeff Amiel wrote:
> --- On Wed, 12/30/09, Jeff Amiel <becauseimjeff@yahoo.com> wrote:
>
>> Subject: PANIC:  right sibling 2019 of block 2018 is not next child of 1937 in index "sl_log_2_idx1"
>>
>
>
> I am assuming a re-index for that particular index will rebuild/fix the index (if it happens again).  Any other
thoughts? 
>
>

It appears you have at least one corrupt block.   Where there's one,
there's often more.

I think i'd do a reindex all.   and Imight even do a pg_dumpall,
re-initdb, and restore said dumpall to be safeest.   to be really safe,
stop pg, and take a file system backup first, incase more serious
problems show up during the reindex or dump process