Re: db corruption/recovery help - Mailing list pgsql-general

From Ed L.
Subject Re: db corruption/recovery help
Date
Msg-id 200506061529.24650.pgsql@bluepolka.net
Whole thread Raw
In response to Re: db corruption/recovery help  (Scott Marlowe <smarlowe@g2switchworks.com>)
Responses Re: db corruption/recovery help  ("Ed L." <pgsql@bluepolka.net>)
List pgsql-general
On Monday June 6 2005 3:17 pm, Scott Marlowe wrote:
> On Mon, 2005-06-06 at 15:16, Ed L. wrote:
> > Someone flipped a breaker switch, and evidently triggered
> > corruption in one of our major clusters:
>
> OK, if postgresql is running on hardware that doe NOT lie
> about fsyncing, and it is set to fsync, this should NEVER
> happen.

This is 7.3.4 running on an HP-UX 11.00 9000/800 PA-RISC box with
fsync = TRUE, built with gcc 3.2.2.  Database is entirely on a
SAN.

We got very lucky:  the corrupted database was expendable
(essentially a log database).  I was able to just move the
data/base/NNNN directory off to the side, restart, drop the
corrupted db, and recreate schema...

Thanks,
Ed

pgsql-general by date:

Previous
From: "Sean Davis"
Date:
Subject: Re: Large Object => invalid input syntax for integer: ""
Next
From: "Ed L."
Date:
Subject: Re: db corruption/recovery help