Message-ID: <5277F277.3090705@pasteleros.org.ar>
Date: Mon, 04 Nov 2013 16:16:07 -0300
From: Alejandro Brust <alejandrob@pasteleros.org.ar>
Reply-To: alejandrob@pasteleros.org.ar
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:17.0) Gecko/20130503 Thunderbird/17.0.5
MIME-Version: 1.0
To: pgsql-admin@postgresql.org
Subject: Re: testing database consistency
References: 
 <CAONrwUGVR_-WwHWqYFAHk0jJEdGV7vEH6Qw2-Lgun2Hzbp53Bg@mail.gmail.com>
In-Reply-To: 
 <CAONrwUGVR_-WwHWqYFAHk0jJEdGV7vEH6Qw2-Lgun2Hzbp53Bg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Hi,
U could try to perform many task over the running copy
like pg_dump + pg_restore + vacuumdb + reindexdb.... ,etc
If all of them  went ok U could make several select of yours best known
tables and compare them with the original one.


see U


El 24/10/2013 04:18, Raphael Bauduin escribió:
> Hi,
>
> I have a postgresql running in a virtual machine (linux, kvm).
> I wanted to test that the backup, which takes a copy of the disk
> image, is valid and usable.
>
> I have taken a copy of the disk image and run it fine on another computer.
> However, just starting the server succesfully does not mean there is
> no corrupted data in the database. This is why I'm looking to a way to
> validate that all the data stored in the postgresql is ok, ie
> consistent and usable. Does anyone have advices on how to best check
> the validity of the whole database?
>
> Thanks in advance!
>
> Raphaël


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin