| Lists: | pgsql-general |
|---|
| 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: | 2009-12-31 00:22:03 |
| Message-ID: | 417408.70946.qm@web65501.mail.ac4.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-general |
--- 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?
| 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: | 2009-12-31 01:05:49 |
| Message-ID: | 4B3BF8ED.3090309@hogranch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-general |
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
| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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