Re: db corruption/recovery help

From: "Ed L(dot)" <pgsql(at)bluepolka(dot)net>
To: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: db corruption/recovery help
Date: 2005-06-06 21:39:55
Message-ID: 200506061539.56097.pgsql@bluepolka.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Monday June 6 2005 3:29 pm, Ed L. wrote:
> 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...

The SAN never lost power, only the system itself. I'd really
like to chase this to the root if possible. Ideas?

Ed

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jochem van Dieten 2005-06-06 21:49:33 Re: pg_dump 8.0.3 failing against PostgreSQL 7.3.2
Previous Message Ed L. 2005-06-06 21:29:24 Re: db corruption/recovery help