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: Jeff Amiel <becauseimjeff(at)yahoo(dot)com>
- To: 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 16:22:03 -0800 (PST)
- Message-id: <417408.70946.qm@web65501.mail.ac4.yahoo.com> <text/plain>
--- 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?
- Follow-Ups:
- Prev by Date: PANIC: right sibling 2019 of block 2018 is not next child of 1937 in index "sl_log_2_idx1"
- Next by Date: Visual DATA editor for PostgreSQL?
- Previous by thread: 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: