Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id D86AD6339EB for ; Fri, 9 Apr 2010 15:03:28 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 50177-04 for ; Fri, 9 Apr 2010 18:03:12 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from gw.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by mail.postgresql.org (Postfix) with ESMTP id DD814632349 for ; Fri, 9 Apr 2010 15:03:14 -0300 (ADT) Received: from Courts-MTA by gw.wicourts.gov with Novell_GroupWise; Fri, 09 Apr 2010 13:03:13 -0500 Message-Id: <4BBF25870200002500030671@gw.wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 8.0.1 Date: Fri, 09 Apr 2010 13:03:03 -0500 From: "Kevin Grittner" To: "pgsql-admin@postgresql.org" , "Khangelani Gama" Subject: Re: Re: database restoration problem- data became incorrect caused by incorrect date in the server References: <4BBEEFF3020000250003063E@gw.wicourts.gov> In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.141 tagged_above=-10 required=5 tests=AWL=-1.131, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201004/119 X-Sequence-Number: 34213 Khangelani Gama wrote: > the backups we have uses pg_dump command. The automatic > backup dumps file happen daily and gets saved in a certain > directory No off-site copies or archives to fall back on? If not, my ideas are: (1) I hope you made a file copy as soon as you found the problem. If not, stop the database and make one immediately. If the old versions of the rows haven't yet been vacuumed away, it might be possible to fish some or all of the corrupted data out of the database. This is very tricky work, though, and you might want to contract with an expert. (I don't do that anymore, but there are several good companies with people who do.) (2) Are there any source documents you can fall back on to reconstruct the data? (3) Is there any way to "reverse" the particular calculations or operations which mangled the data? Once you do get upgraded, you should look into Point In Time Recovery (PITR) backups. Had you been running this, you could have replayed the transactions right up to the moment of corruption. Well, if you kept a base backup from before the corruption and all the WAL files since that base backup. -Kevin