Received: from maia.hub.org (maia-3.hub.org [200.46.204.243])
	by mail.postgresql.org (Postfix) with ESMTP id 745291337B39
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Mon, 29 Nov 2010 20:02:25 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia,
	port 10024) with ESMTP id 67566-07 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Tue, 30 Nov 2010 00:02:14 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by mail.postgresql.org (Postfix) with ESMTP id D57571335B36
	for <pgsql-admin@postgresql.org>; Mon, 29 Nov 2010 20:02:13 -0400 (AST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id oAU02CoD007754;
	Mon, 29 Nov 2010 19:02:12 -0500 (EST)
To: Anderson Valadares <andervalbh@gmail.com>
cc: pgsql-admin@postgresql.org
Subject: Re: failed to re-find parent key in index "22723655" for split pages
	370836/370837
In-reply-to: <AANLkTik-zUw1KdtKHvK362FauXe8uOUAyRuiN=9vmB4z@mail.gmail.com> 
References: <AANLkTik-zUw1KdtKHvK362FauXe8uOUAyRuiN=9vmB4z@mail.gmail.com>
Comments: In-reply-to Anderson Valadares <andervalbh@gmail.com>
	message dated "Mon, 29 Nov 2010 19:15:22 -0200"
Date: Mon, 29 Nov 2010 19:02:12 -0500
Message-ID: <7753.1291075332@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201011/242
X-Sequence-Number: 36208

Anderson Valadares <andervalbh@gmail.com> writes:
>  I am facing problems starting the database. Following is the error message.
> Can anyone help me?

> 2010-11-29 18:12:41 BRST [] - [5011]: [14-1] FATAL:  XX000: failed to
> re-find parent key in index "22723655" for split pages 370836/370837

The only way you're going to get out of that is with pg_resetxlog,
which is a fairly blunt instrument :-(.  It's possible that you will
have database corruption afterwards.  I'd recommend doing a dump and
reload to see if any problems appear.  It'd also be a good idea to save
a tarball copy of the $PGDATA file tree beforehand, so at least you can
get back to where you are in case things turn into a complete mess.

Can you tell us anything about how you got into this state?

			regards, tom lane