Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id SAA48464 for ; Fri, 24 Sep 1999 18:43:15 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id SAA07133; Fri, 24 Sep 1999 18:42:09 -0400 (EDT) To: Clayton Cottingham cc: pgsql-sql@postgreSQL.org Subject: Re: [SQL] pg_dumpall + psql -e template1 In-reply-to: Your message of Fri, 24 Sep 1999 21:47:14 +0000 <37EBF162.867DC57E@smartt.com> Date: Fri, 24 Sep 1999 18:42:09 -0400 Message-ID: <7131.938212929@sss.pgh.pa.us> From: Tom Lane Clayton Cottingham writes: > when i dump out all dbspg_dumpall>dbs.out and try to put into a new > installation psql -e template1 copy the actual data > usually producing errors that result in the \? listings and then a seq > fault There have been some reports that COPY in/out is not careful enough about quoting control characters and so forth, so if you have text fields containing control characters you might run into a problem like the above. As a quick workaround, try the pg_dump switch to dump data as INSERT statements instead of with COPY. It'll be a lot slower to load :( but if it avoids the problem then this is probably the correct diagnosis. If you can track down exactly what data is making COPY misbehave, we'd have a better shot at fixing the bug. regards, tom lane