Sender: hannu@kodu.home.ee
Message-ID: <379F8913.DCFE646E@trust.ee>
Date: Thu, 29 Jul 1999 01:49:55 +0300
From: Hannu Krosing <hannu@trust.ee>
Organization: Trust-O-Matic =?iso-8859-1?Q?O=DC?=
MIME-Version: 1.0
To: "G. Anthony Reina" <reina@nsi.edu>
CC: pgsql-hackers@postgreSQL.org
Subject: Re: [HACKERS] pg_dump not dumping all tables
References: <379F821C.761F6334@nsi.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"G. Anthony Reina" wrote:
> 
> I just installed 6.5.1 on my RH 6.0 PII/400 MHz machine. I had
> previously been running the database on 6.4.2 and had several backups
> made through pgdump. When I tried to restore the database (i.e. psql -e
> db01 < db.backup) all of the tables were created, but only some of them
> had data. These tables are just real tables, not views or anything
> strange. Luckily, I also had a back up where I had pg_dump'ed each table
> separately (so I'm not in a total jam). But I can't figure out why the
> pg_dump didn't backup all of the data.
> 
> -Tony Reina

If there is even one row dumped wrong the data for the whole table is
not 
inserted ;(

I've had this for row's containing \n (or maybe \r) that got dumped as
real 
newline that screwed the whole COPY xxx FROM stdin. 
I resolved it by editing the dumpfile via visual inspection.

Another thing to try would be to dump as proper insert strings (pg_dump
-d) 
instead of copy from. It will be slow to load though ...

---------------------------
Hannu