Re: Crash Recovery

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Noah Silverman <noah(at)allresearch(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Crash Recovery
Date: 2003-01-24 06:29:35
Message-ID: 10919.1043389775@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Noah Silverman <noah(at)allresearch(dot)com> writes:
> I'm curious about where I can find documentation about crash recovery in
> postgres. In mysql, there is a nice table recovery utility (myisamchk).
> is there something similar in postgres?

There are no automated recovery tools for Postgres, because there are
no known failure modes that are systematic enough to allow automatic
recovery. We prefer to fix such bugs rather than patch around them.

There are some last-ditch tools for reconstructing indexes (REINDEX)
and for throwing away the WAL log (pg_resetxlog) but I have not seen
any recent cases where I would have felt that blind invocation of either
would be a good move.

> What do we do if a table or
> database becomes corrupted? (I'm aware of backup techniques, but it isn't
> feasible for some of our larger tables.

Reconsider that. If your data center burns down tonight, what is your
fallback? Ultimately, you *must* have a backup copy, or you're just not
taking the possibility of failure seriously.

regards, tom lane

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2003-01-24 06:48:19 Re: Does "correlation" mislead the optimizer on large tables?
Previous Message Ron Mayer 2003-01-24 04:16:09 Does "correlation" mislead the optimizer on large tables?