Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Wed, 30 Dec 2009 20:08:30 -0500
- Message-id: <4B3BF98E.4030703@2ndquadrant.com> <text/plain>
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
- References:
- Prev by Date: Re: PANIC: right sibling 2019 of block 2018 is not next child of 1937 in index "sl_log_2_idx1"
- Next by Date: Re: Visual DATA editor for PostgreSQL?
- Previous by thread: Re: PANIC: right sibling 2019 of block 2018 is not next child of 1937 in index "sl_log_2_idx1"
- Next by thread: Visual DATA editor for PostgreSQL?
- Indexes: