From: Benjamin Wragg <bwragg@tpg.com.au>
To: 'Bruce Momjian' <pgman@candle.pha.pa.us>
To: 'Mike Miller' <temp6453@hotmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Restoring pg_dump's made using COPY commands
Date: Wed, 18 Feb 2004 08:58:24 +1030
Message-ID: <002401c3f5a5$5be3a380$0200a8c0@mapping12> (raw)
In-Reply-To: <200402171619.i1HGJ2c18481@candle.pha.pa.us>
I had this problem just yesterday. I found it was due to an error a few
lines before my copy command started.
-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Bruce Momjian
Sent: Wednesday, 18 February 2004 2:49 AM
To: Mike Miller
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Restoring pg_dump's made using COPY commands
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
> <occasionally messages about missing fields>
>
> 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
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: bwragg@tpg.com.au, pgman@candle.pha.pa.us, temp6453@hotmail.com
Subject: Re: Restoring pg_dump's made using COPY commands
In-Reply-To: <002401c3f5a5$5be3a380$0200a8c0@mapping12>
References: <200402171619.i1HGJ2c18481@candle.pha.pa.us> <002401c3f5a5$5be3a380$0200a8c0@mapping12>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox