Skip site navigation (1) Skip section navigation (2)

Re: Restoring pg_dump's made using COPY commands

From: "Benjamin Wragg" <bwragg(at)tpg(dot)com(dot)au>
To: "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us>,"'Mike Miller'" <temp6453(at)hotmail(dot)com>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Restoring pg_dump's made using COPY commands
Date: 2004-02-17 22:28:24
Message-ID: 002401c3f5a5$5be3a380$0200a8c0@mapping12 (view raw or flat)
Thread:
Lists: pgsql-admin
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(at)postgresql(dot)org
[mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of Bruce Momjian
Sent: Wednesday, 18 February 2004 2:49 AM
To: Mike Miller
Cc: pgsql-admin(at)postgresql(dot)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(at)candle(dot)pha(dot)pa(dot)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(at)postgresql(dot)org so that your
      message can get through to the mailing list cleanly


In response to

pgsql-admin by date

Next:From: Tom LaneDate: 2004-02-17 23:45:03
Subject: Re: how to recover corrupt data
Previous:From: WendellDate: 2004-02-17 20:40:10
Subject: problem with install config

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group