Re: Reseting undo/redo logs - Mailing list pgsql-hackers

From Edmon Begoli
Subject Re: Reseting undo/redo logs
Date
Msg-id CAGj+Yse0F_BscOrYXpTQZDWicJwVJNuyMGi=TC8ZFKCjiDskBA@mail.gmail.com
Whole thread Raw
In response to Re: Reseting undo/redo logs  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Thanks. I was going down this route, so just your confirmation that
this is the right path is helpful.

Edmon

On Thu, Jun 21, 2012 at 11:58 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Edmon Begoli <ebegoli@gmail.com> writes:
>> One of the Greenplum segments went down and it cannot recover because
>> "PANIC        XX000 invalid redo/undo record in shutdown checkpoint
>> (xlog.c:6576)"
>
>> I am posting this question here because most casual users of
>> Postgres/Greenplum are telling me that database is hosed, but I think
>> that with pg_resetxlog and some
>> (http://www.postgresql.org/docs/8.2/static/app-pgresetxlog.html) data
>> loss I could at least "hack" database to come back up.
>
>> What I am asking for help here is to help me calculate the reset
>> values - where to find the most recent valid one and how to
>> *specifically* calculate the reset ones.
>
> pg_controldata should give you useful starting points.  I don't think we
> can offer any more help than what is on the pg_resetxlog reference page
> as to what to do with them.  (Though you might try reading the more
> recent releases' versions of that page to see if anything's been
> clarified.)
>
>                        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Reseting undo/redo logs
Next
From: Tom Lane
Date:
Subject: Re: COMMUTATOR doesn't seem to work