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: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: right sibling is not next child
Date: 2006-04-12 16:40:27
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
Per the DBAs, there hadn't been any recent crashes before last Thursday.
 A "vacuum analyze verbose" discovered the problem early Thursday
morning.  After the PANIC, the database never came back up (the
heap_clean_redo: no block / full_page_writes = off problem).

One thing that seems strange to me is that the original crash on
Thursday failed on Panel_pkey, but my "vacuum analyze verbose" on a copy
of the crashed database failed on MaintCode /

I'll send over pg_statistic_relid_att_index and Panel_pkey.  Showing
the keys to Panel_pkey is no problem.


>>> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 04/12/06 6:03 pm >>>
You did say that this problem showed up shortly after a database

Could you send me a copy of pg_statistic_relid_att_index, off-list
(the actual disk file, not a pg_filedump)?  There's nothing but table
OIDs and attribute numbers in it, so I can't see any reason anyone
would consider it sensitive data.  I've got some really crude code
laying about for scanning an index and looking for inconsistencies ...
it's too ugly to give out, but I'd like to see if it can find anything
wrong with that index.  (I'll probably ask for a copy of Panel_pkey
for the same purpose, if you get permission to show us its keys.)

			regards, tom lane

In response to


pgsql-bugs by date

Next:From: Tom LaneDate: 2006-04-12 20:28:41
Subject: Re: right sibling is not next child
Previous:From: Tom LaneDate: 2006-04-12 16:03:12
Subject: Re: right sibling is not next child

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