Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id DF4D39FB226 for ; Mon, 8 Jan 2007 13:25:48 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 12808-09 for ; Mon, 8 Jan 2007 13:25:22 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id CF2759FB223 for ; Mon, 8 Jan 2007 13:25:21 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id l08HPJhZ011773; Mon, 8 Jan 2007 12:25:19 -0500 (EST) To: "Chris Hoover" cc: "pgsql-admin@postgresql.org" Subject: Re: 8.1.3 Crash/Corruption Problem In-reply-to: <1d219a6f0701080841l3a795a08se3852c23bea2e240@mail.gmail.com> References: <1d219a6f0701080841l3a795a08se3852c23bea2e240@mail.gmail.com> Comments: In-reply-to "Chris Hoover" message dated "Mon, 08 Jan 2007 11:41:30 -0500" Date: Mon, 08 Jan 2007 12:25:19 -0500 Message-ID: <11772.1168277119@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/65 X-Sequence-Number: 24221 "Chris Hoover" writes: > Over the weekend, I suffered from major database corruption on my > 8.1.3database. Fortunetly, this was my development/non-production box > so I did > not have to spend my entire weekend getting it back online, but I did spend > a major portion of it. I ended up having to do a pitr recovery of the > system. I don't understand what happened to the system. Please help > explain what happened. Also, would there have been another option to get > the system back online w/o the full recovery? This looks like a problem we fixed in 8.1.6 ... consider updating. regards, tom lane