Re: CRITICAL HELP NEEDED! DEAD DB! - Mailing list pgsql-hackers

From Dann Corbit
Subject Re: CRITICAL HELP NEEDED! DEAD DB!
Date
Msg-id D425483C2C5C9F49B5B7A41F894415470554E0@postal.corporate.connx.com
Whole thread Raw
In response to CRITICAL HELP NEEDED! DEAD DB!  (Cott Lang <cott@internetstaff.com>)
Responses Re: CRITICAL HELP NEEDED! DEAD DB!
List pgsql-hackers
> -----Original Message-----
> From: pgsql-hackers-owner@postgresql.org
> [mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of Cott Lang
> Sent: Friday, September 24, 2004 10:21 AM
> To: pgsql-hackers@postgresql.org
> Subject: [HACKERS] CRITICAL HELP NEEDED! DEAD DB!
>
>
> Sep 24 10:22:37 snafu postgres[18306]: [2-1] LOG:  database
> system was interrupted while in recovery at 2004-09-24
> 10:21:41 MST Sep 24 10:22:37 snafu postgres[18306]: [2-2]
> HINT:  This probably means that some data is corrupted and
> you will have to use the last backup for recovery. Sep 24
> 10:22:37 snafu postgres[18306]: [3-1] LOG:  checkpoint record
> is at 9A/C2022368 Sep 24 10:22:37 snafu postgres[18306]:
> [4-1] LOG:  redo record is at 9A/C2022368; undo record is at
> 0/0; shutdown FALSE Sep 24 10:22:37 snafu postgres[18306]:
> [5-1] LOG:  next transaction ID: 197841225; next OID:
> 715436086 Sep 24 10:22:37 snafu postgres[18306]: [6-1] LOG:
> database system was not properly shut down; automatic
> recovery in progress Sep 24 10:22:37 snafu postgres[18306]:
> [7-1] LOG:  redo starts at 9A/C20223B0 Sep 24 10:22:37 snafu
> postgres[18306]: [8-1] PANIC:  btree_insert_redo: failed to
> add item Sep 24 10:22:37 snafu postgres[18299]: [2-1] LOG:
> startup process (PID
> 18306) was terminated by signal 6
> Sep 24 10:22:37 snafu postgres[18299]: [3-1] LOG:  aborting
> startup due to startup process failure
>
>
> Any suggestions to recover?!  I'm dead in the water!  Please!!!

When did you do your last backup?

This message is a clue:
"HINT:  This probably means that some data is corrupted and you will
have to use the last backup for recovery."

If you do a restore from your last backup, you will lose the data
between that time and the time of the problem.  Any other solution will
be fraught with peril, I think.

Otherwise, maybe something here will help:
http://svana.org/kleptog/pgsql/pgfsck.html


pgsql-hackers by date:

Previous
From: Cott Lang
Date:
Subject: CRITICAL HELP NEEDED! DEAD DB!
Next
From: Tom Lane
Date:
Subject: Re: CRITICAL HELP NEEDED! DEAD DB!