Skip site navigation (1) Skip section navigation (2)

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

From: Greg Smith <greg(at)2ndquadrant(dot)com>
To: John R Pierce <pierce(at)hogranch(dot)com>
Cc: Jeff Amiel <becauseimjeff(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: PANIC: right sibling 2019 of block 2018 is not next child of 1937 in index "sl_log_2_idx1"
Date: 2009-12-31 01:08:30
Message-ID: 4B3BF98E.4030703@2ndquadrant.com (view raw or flat)
Thread:
Lists: pgsql-general
John R Pierce wrote:
> 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

I would add a basic check of the system hardware to that list.  In 
particular, I'm always suspicious of memory errors when seeing strange 
PANIC messages.  A quick check for SMART errors on the hard drives would 
be in order too.

-- 
Greg Smith    2ndQuadrant   Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com  www.2ndQuadrant.com


In response to

pgsql-general by date

Next:From: Craig RingerDate: 2009-12-31 01:13:16
Subject: Re: Visual DATA editor for PostgreSQL?
Previous:From: John R PierceDate: 2009-12-31 01:05:49
Subject: Re: PANIC: right sibling 2019 of block 2018 is not next child of 1937 in index "sl_log_2_idx1"

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group