pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
To: Khangelani Gama <Khangelani.Gama@ucs-software.co.za>
Subject: Re: Re: database restoration problem- data became incorrect caused by incorrect date in the server
Date: Fri, 09 Apr 2010 13:03:03 -0500
Message-ID: <4BBF25870200002500030671@gw.wicourts.gov> (raw)
In-Reply-To: <D78A8169F9436B4DB978300336168F3B3359A3AB7C@SWBREXCH00.ucs-software.net>
References: <D78A8169F9436B4DB978300336168F3B3359A3A9F7@SWBREXCH00.ucs-software.net>
	<D78A8169F9436B4DB978300336168F3B3359A3AA3B@SWBREXCH00.ucs-software.net>
	<4BBEEFF3020000250003063E@gw.wicourts.gov>
	<D78A8169F9436B4DB978300336168F3B3359A3AB7C@SWBREXCH00.ucs-software.net>

Khangelani Gama <Khangelani.Gama@ucs-software.co.za> 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



view thread (6+ messages)  latest in thread

Message-ID: <4BBF25870200002500030671@gw.wicourts.gov>
Permalink:  ../4BBF25870200002500030671@gw.wicourts.gov/
Also on:    postgresql.org/message-id/4BBF25870200002500030671@gw.wicourts.gov

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: Kevin.Grittner@wicourts.gov, Khangelani.Gama@ucs-software.co.za
  Subject: Re: database restoration problem- data became incorrect caused by incorrect date in the server
  In-Reply-To: <4BBF25870200002500030671@gw.wicourts.gov>
  References: <D78A8169F9436B4DB978300336168F3B3359A3A9F7@SWBREXCH00.ucs-software.net> <D78A8169F9436B4DB978300336168F3B3359A3AA3B@SWBREXCH00.ucs-software.net> <4BBEEFF3020000250003063E@gw.wicourts.gov> <D78A8169F9436B4DB978300336168F3B3359A3AB7C@SWBREXCH00.ucs-software.net> <4BBF25870200002500030671@gw.wicourts.gov>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox