Received: from nsi.edu (amethea.nsi.edu [198.133.185.9])
	by hub.org (8.9.3/8.9.3) with ESMTP id SAA67155
	for <pgsql-hackers@postgreSQL.org>;
	Wed, 28 Jul 1999 18:47:54 -0400 (EDT) (envelope-from reina@nsi.edu)
Received: from nsi.edu (o21.nsi.edu [204.128.156.216])
	by nsi.edu (8.9.1/8.9.1) with ESMTP id PAA23786;
	Wed, 28 Jul 1999 15:47:48 -0700 (PDT)
Sender: reina@nsi.edu
Message-ID: <379F89A5.B92D36FA@nsi.edu>
Date: Wed, 28 Jul 1999 15:52:22 -0700
From: "G. Anthony Reina" <reina@nsi.edu>
Organization: The Neurosciences Institute
X-Mailer: Mozilla 4.07C-SGI [en] (X11; I; IRIX 6.5 IP32)
MIME-Version: 1.0
To: Hannu Krosing <hannu@trust.ee>,
	"pgsql-hackers@postgreSQL.org" <pgsql-hackers@postgreSQL.org>
Subject: Re: [HACKERS] pg_dump not dumping all tables
References: <379F821C.761F6334@nsi.edu> <379F8913.DCFE646E@trust.ee>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hannu Krosing wrote:

> 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,

    Unfortunately, my dump file is 2 Gig and so I can't edit it easily. I
don't mind slowness as long as I have accuracy so I'll try the pg_dump -d.

Thanks.
-Tony