| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Mark Spruill" <mark(dot)spruill(at)mightyautoparts(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Dump produces file with new line characters |
| Date: | 2004-06-23 20:26:04 |
| Message-ID: | 5212.1088022364@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Mark Spruill" <mark(dot)spruill(at)mightyautoparts(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Calvin Mitcham | 2004-06-23 21:21:16 | Re: pgHoster.com woes and looking for a new host |
| Previous Message | Mark Spruill | 2004-06-23 20:03:13 | Dump produces file with new line characters |