From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | swampler(at)noao(dot)edu |
Cc: | Postgres-General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Best way to recover from crash? |
Date: | 2004-07-22 17:59:36 |
Message-ID: | 10818.1090519176@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Steve Wampler <swampler(at)noao(dot)edu> writes:
> Immediately after finally deploying our PG database up
> on our mountain-top observatory, we got hit by lightening.
> (The machines were *supposed* to be installed on a RUPS,
> but weren't. Sigh)
> A file was lost. Now many simple commands cause the
> DB to 'crash':
> I do nightly backups of the DBs so aside from observing time
> lost this isn't catestrophic, but since it takes so long to
> restore from backup (some of the DBs are fairly large) I was
> wondering if there's a 'known procedure' for quickly recovering
> from the above.
I think you'd be foolish not to initdb and reload from the backups.
You have no way to know how extensive the data damage is ... you might
work around the problems you see now, only to find something else
later after you've put more data into the corrupted DB.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Wampler | 2004-07-22 18:04:23 | Re: Best way to recover from crash? |
Previous Message | Harald Fuchs | 2004-07-22 15:44:33 | Re: polating (insert into...) a table with determined record from another table. |