Message-ID: <4CAAC81B.7030205@lelarge.info>
Date: Tue, 05 Oct 2010 08:39:23 +0200
From: Guillaume Lelarge <guillaume@lelarge.info>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); fr;
	rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: =?ISO-8859-1?Q?F=E1bio_Gibon_-_Comex_System?=
 <gibon@comexsystem.com.br>
CC: PostgreSQL - mailing list <pgsql-admin@postgresql.org>
Subject: Re: Validade dump file
References: <120c01cb643d$cb46ab60$aadd5bbb@gibon>
In-Reply-To: <120c01cb643d$cb46ab60$aadd5bbb@gibon>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

Le 05/10/2010 05:28, Fábio Gibon - Comex System a écrit :
> [...]
> are there some tool or internal program that read a dump file (created by pg_dump) and list all tables and number of tuples (without 
> restore) in this file?
> 

That command should give you the number of tables in your plain dump:

  grep "CREATE TABLE" your_dump_file | wc -l

If you have a binary dump (ie, tar or custom), you should do this:

  pg_restore -s your_dump_file | grep "CREATE TABLE" | wc -l

There's no easy way to get the number of tuples in each table.

> And too, are there some tool to check the physical file integrity? (S.O. Windows)

notepad? :)

I mean, with a SQL file, this is just a bunch of SQL queries. So there's
no real way to check the file integrity without restoring it.

On a binary dump, you can do a "pg_restore your_dump_file > /dev/null".
It should warn you if you have an integrity issue.


-- 
Guillaume
 http://www.postgresql.fr
 http://dalibo.com