Dump produces file with new line characters

[Mark Spruill]

This is probably a newbie question but here goes:

We are using Postgres 7.3 on Red Hat 9. We are doing dumps with a script that does:

pg_dump databasename > outfile 2>> logfile

The resulting dump files occasionally have a \N at the end of a line of data following the copy command. This causes a problem when I try to load them back in bacause psql thinks the \N (a new line character?) is a psql command. So, how do I avoid the \N in the dump and/or ignore it in the reload?

Any help would be much appreciated.

Mark Spruill

770.448.3900
ma**********@mightyautoparts.com
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

[Tom Lane]

"Mark Spruill" <ma**********@mightyautoparts.com> writes:

We are using Postgres 7.3 on Red Hat 9. We are doing dumps with a script that does:
pg_dump databasename > outfile 2>> logfile
The resulting dump files occasionally have a \N at the end of a line of data following the copy command. This causes a problem when I try to load them back in bacause psql thinks the \N (a new line character?) is a psql command. So, how do I avoid the \N in the dump and/or ignore it in the reload?

This is a new one on me. Can you show a specific example?

Also, 7.3.what exactly?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster