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: John R Pierce <pierce(at)hogranch(dot)com>
- To: Jeff Amiel <becauseimjeff(at)yahoo(dot)com>
- Cc: 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 17:05:49 -0800
- Message-id: <4B3BF8ED.3090309@hogranch.com> <text/plain>
Jeff Amiel wrote:
--- On Wed, 12/30/09, Jeff Amiel <becauseimjeff(at)yahoo(dot)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
- Follow-Ups:
- References:
- Prev by Date: Visual DATA editor for PostgreSQL?
- Next by Date: Re: PANIC: right sibling 2019 of block 2018 is not next child of 1937 in index "sl_log_2_idx1"
- 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: Re: PANIC: right sibling 2019 of block 2018 is not next child of 1937 in index "sl_log_2_idx1"
- Indexes: