Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 2488847609C for ; Fri, 24 Jan 2003 02:08:57 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 0967647669A for ; Fri, 24 Jan 2003 01:29:37 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h0O6Ta5u010920; Fri, 24 Jan 2003 01:29:36 -0500 (EST) To: Noah Silverman Cc: pgsql-performance@postgresql.org Subject: Re: Crash Recovery In-reply-to: <2147483647.1043361178@[10.0.1.133]> References: <2147483647.1043361178@[10.0.1.133]> Comments: In-reply-to Noah Silverman message dated "Thu, 23 Jan 2003 22:32:58 -0500" Date: Fri, 24 Jan 2003 01:29:35 -0500 Message-ID: <10919.1043389775@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/276 X-Sequence-Number: 923 Noah Silverman 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