From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
---|---|
To: | m(dot)sakrejda(at)gmail(dot)com, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #10432: failed to re-find parent key in index |
Date: | 2014-05-27 18:06:34 |
Message-ID: | 5384D42A.8070904@vmware.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 05/23/2014 08:52 PM, m(dot)sakrejda(at)gmail(dot)com wrote:
> I just got the error `failed to re-find parent key in index "1665279" for
> split pages 175193/193740`. From the list archives [1], it looks like
> there's no easy recovery, but this happened on a replica right after the
> recovery trigger file was touched and recovery completed, so that's not a
> huge concern (unless it also happens to the next replica). Is there
> something to be learned from the failed cluster?
I would be interested in seeing the structure of the index, if there is
anything else corrupt in there. Also, what WAL actions led to the error?
Try something like:
pg_xlogdump -r btree -p $PGDATA -s 339/65000000 | grep 1665279
and search that for any records related to the failed split, e.g.
grepping further for the block numbers in the error message.
- Heikki
From | Date | Subject | |
---|---|---|---|
Next Message | Honza Horak | 2014-05-28 08:07:24 | Re: postgresql test failure with Python 3.4.0 in plpython_do |
Previous Message | Graeme | 2014-05-27 17:00:37 | ./configure failure under Mageia 4 x86_64 |