X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id C6746D1DA83 for ; Tue, 17 Feb 2004 16:20:30 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 14597-09 for ; Tue, 17 Feb 2004 12:20:25 -0400 (AST) Received: from candle.pha.pa.us (candle.pha.pa.us [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id DE6CBD1DF85 for ; Tue, 17 Feb 2004 12:20:23 -0400 (AST) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id i1HGJ2c18481; Tue, 17 Feb 2004 11:19:02 -0500 (EST) From: Bruce Momjian Message-Id: <200402171619.i1HGJ2c18481@candle.pha.pa.us> Subject: Re: Restoring pg_dump's made using COPY commands In-Reply-To: To: Mike Miller Date: Tue, 17 Feb 2004 11:19:02 -0500 (EST) Cc: pgsql-admin@postgresql.org X-Mailer: ELM [version 2.4ME+ PL108 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/255 X-Sequence-Number: 12429 Mike Miller wrote: > Hi, > I'm trying to restore two dumps, one from 7.1.3 and the other from a 6.5.3 > series PgSQL server. These dumps were both made using standard 'pg_dump > > output' commands (specifying the host where needed on one of them). When I > run the database restore by doing execute-file in psql, piping the file to > psql, or even attempting pg_restore (whcih doesn't work on these plain text > databases), I receive messages pertaining to: > invalid command \N > invalid command \. > parse error at the end of line > > > However this dump just came from a pg_dump, so it really should be working. > I've tried every combination of pg_dump and psql versions from 7.4.1, 7.3.3, > 7.1.3, 6.5.3 in order to get this to work right without any luck. > > Can anyone help me out with what is wrong? I'm looking to make this a > backup method, and if I can't restore the data, it doesn't do me much good > (and I'm trying to restore some existing data). Ultimately want to move > them all up to 7.4.x > > Any ideas as to what causes these errors? Anything I can do to fix the > output of pg_dump? Strange. We used \N for NULLs way back in 6.5 and earlier. I wonder if you have carriage returns in the file accidentally. Any way to see the lines that are failing? -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073