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: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: pgsql-bugs(at)postgresql(dot)org, "Peter Brant" <Peter(dot)Brant(at)wicourts(dot)gov>, "Randy Peterson" <Randy(dot)Peterson(at)wicourts(dot)gov>
Subject: Re: right sibling is not next child
Date: 2006-04-06 18:48:22
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote: 
>> Anyway, that explains your "heap_clean_redo: no block" failure.  I think
>> you're stuck risking a pg_resetxlog to try to get back into the
>> database.

> Will do.  Before I do that, though, is it worth making a copy?  (The
> down side is primarily the delay of copying it.)

Yeah, I think you'd better --- pg_resetxlog is destructive, and if we
find the database unusable for debugging afterward, we'll need that

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Stephan SzaboDate: 2006-04-06 21:56:25
Subject: Re: BUG #2377: pg_constraint didnt't updated when table
Previous:From: Kevin GrittnerDate: 2006-04-06 18:45:22
Subject: Re: right sibling is not next child

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