Skip site navigation (1) Skip section navigation (2)

Re: right sibling is not next child

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Peter Brant" <Peter(dot)Brant(at)wicourts(dot)gov>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: right sibling is not next child
Date: 2006-04-11 23:06:05
Message-ID: 11927.1144796765@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"Peter Brant" <Peter(dot)Brant(at)wicourts(dot)gov> writes:
> I ended up modifying the elog again with the following results:
> PANIC:  right sibling is not next child in "Panel_pkey", parent is 271,
> target is 635, rightsib is 629, nextoffset is 87

OK, so the part of the pg_filedump info we need to see is items 86/87
in block 271, plus a few around them for good measure.

Are the values of the keys in this index sensitive data, or are they
just serial numbers of some kind?  If we could see pg_dump -i -f rather
than just -i, it might help.  I'd like to see the dumps of pages 635,
636, 629 as well (mostly their "special space" contents).

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Peter BrantDate: 2006-04-11 23:38:20
Subject: Re: right sibling is not next child
Previous:From: Peter BrantDate: 2006-04-11 22:59:13
Subject: Re: right sibling is not next child

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group