pg_dump errors

From: Richard Hodges <rh(at)matriplex(dot)com>
To: pgsql-docs(at)postgresql(dot)org
Subject: pg_dump errors
Date: 2001-08-30 20:27:45
Message-ID: Pine.BSF.4.10.10108301318120.79095-100000@mail.matriplex.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

I have just spent some time frustrated with a pg_dump problem. My goal was
simply to copy data from two 7.0.3 tables to a new 7.1.2 database. The
symptom was a (nearly) endless series of "invalid command \N" error
messages when trying to "restore" into the new database.

I could find maybe a dozen or so references on Google, and none of them
seemed to give me the information I needed to solve this problem.
Finally, I ran across one message suggesting that using the "-d" option
("Dump data as proper insert strings") with pg_dump would avoid the
errors. Sure enough, it works.

The "PostgreSQL User's Guide" does list the "-d" option for pg_dump, but I
don't see how one would find out that this is the solution to the "invalid
command \N" problem. Perhaps this would be an appropriate addition to the
FAQ?

Thanks,

-Richard

-------------------------------------------
Richard Hodges | Matriplex, inc.
Product Manager | 769 Basque Way
rh(at)matriplex(dot)com | Carson City, NV 89706
775-886-6477 | www.matriplex.com

Browse pgsql-docs by date

  From Date Subject
Next Message Horace A. Vallas, Jr. 2001-08-30 20:56:21 pg_dump manual?
Previous Message Peter Eisentraut 2001-08-30 14:43:00 Commit docbook2man?