Re: corrupted pg_xlog/0000000000000000

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Scott Parish <sRp(at)srparish(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: corrupted pg_xlog/0000000000000000
Date: 2001-02-27 04:06:03
Message-ID: 27961.983246763@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Scott Parish <sRp(at)srparish(dot)net> writes:
> I have a production database running postgresql 7.1beta4. Everything
> was great untill '/etc/rc.d/init.d/pgsql stop' was ran. Now when ever a
> person makes an attempt to start the database postmaster refuses to
> start saying:

> DEBUG: starting up
> DEBUG: database system was interrupted at 2001-02-26 14:34:09
> DEBUG: CheckPoint record at (0, 5962224)
> FATAL 2: Invalid RMID in checkPoint record

Hmm, that was after a successful shutdown!? Ugh.

> Are there any suggestions on how i may go about recovering from this
> incident without starting from scratch?

I'm planning to take a hard look at WAL robustness over the next day or
two, but if you need to get this DB back in production right now then
I'm afraid you have little choice but initdb.

It would be good if you could save aside the current contents of the
data directory as a test case for the repaired code, though. Even
better, could you send me the contents of your pg_xlog directory (or
maybe even the whole database if it's not very large) for debugging
purposes?

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Richardson 2001-02-27 05:47:12 Case sensitivity
Previous Message Tatsuo Ishii 2001-02-27 03:41:42 Re: Re: local mailing lists