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

Re: right sibling is not next child

From: "Peter Brant" <Peter(dot)Brant(at)wicourts(dot)gov>
To: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: right sibling is not next child
Date: 2006-04-11 18:48:23
Message-ID: 443BB3A7020000BE00002C14@gwmta.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-bugs
Sorry about the delay in responding.  We had a bit of difficulty with
the test machine.  Kevin is also on vacation this week.

The problem is repeatable with a VACUUM.  I've found the offending
block.  A (partial) pg_filedump of that block is pasted in below.  I'm a
little lost as to what the next step is though.  Any pointers would be
appreciated.

Pete

"Kevin Grittner" <Kevin ( dot ) Grittner ( at ) wicourts ( dot ) gov>
writes:
> [2006-04-06 02:19:57.460 ] 3848 <postgres bigbird 127.0.0.1(3944)>
PANIC:  right sibling is not next child in "Panel_pkey"

This should be repeatable by re-attempting a VACUUM, right?  Please
find
out which page exactly it's unhappy about (either gdb the crash or add
a
printout of the "parent" variable to the elog call in nbtpage.c), then
pg_filedump the index and look to see what the index contains.

			regards, tom lane

PANIC:  right sibling is not next child in "Panel_pkey", parent is 271

*******************************************************************
* PostgreSQL File/Block Formatted Dump Utility - Version 8.1.1
*
* File: 180571
* Options used: -R 271 -i 
*
* Dump created on: Tue Apr 11 13:38:44 2006
*******************************************************************

Block  271 ********************************************************
<Header> -----
 Block Offset: 0x0021e000         Offsets: Lower     468 (0x01d4)
 Block: Size 8192  Version    3            Upper    1952 (0x07a0)
 LSN:  logid    246 recoff 0x265d47c0      Special  8176 (0x1ff0)
 Items:  112                   Free Space: 1484
 Length (including item array): 472

<Data> ------ 
 Item   1 -- Length:   56  Offset: 8120 (0x1fb8)  Flags: USED
  Block Id: 132  linp Index: 1  Size: 56
  Has Nulls: 0  Has Varwidths: 16384

 Item   2 -- Length:    8  Offset: 8112 (0x1fb0)  Flags: USED
  Block Id: 201  linp Index: 1  Size: 8
  Has Nulls: 0  Has Varwidths: 0

 Item   3 -- Length:   56  Offset: 8056 (0x1f78)  Flags: USED
  Block Id: 257  linp Index: 1  Size: 56
  Has Nulls: 0  Has Varwidths: 16384

... snip ...

 Item 109 -- Length:   56  Offset: 4920 (0x1338)  Flags: USED
  Block Id: 121  linp Index: 1  Size: 56
  Has Nulls: 0  Has Varwidths: 16384

 Item 110 -- Length:   56  Offset: 4864 (0x1300)  Flags: USED
  Block Id: 133  linp Index: 1  Size: 56
  Has Nulls: 0  Has Varwidths: 16384

 Item 111 -- Length:   56  Offset: 4808 (0x12c8)  Flags: USED
  Block Id: 134  linp Index: 1  Size: 56
  Has Nulls: 0  Has Varwidths: 16384

 Item 112 -- Length:   56  Offset: 4752 (0x1290)  Flags: USED
  Block Id: 137  linp Index: 1  Size: 56
  Has Nulls: 0  Has Varwidths: 16384


<Special Section> -----
 BTree Index Section:
  Flags: 0x0000 ()
  Blocks: Previous (167)  Next (455)  Level (1)


*** End of Requested Range Encountered. Last Block Read: 271 ***



Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2006-04-11 19:19:53
Subject: Re: right sibling is not next child
Previous:From: Hugo QuisbertDate: 2006-04-11 16:25:57
Subject: BUG #2388: PostsgreSQL fails under isntallation

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