"Mark Spruill" <mark.spruill@mightyautoparts.com> writes:
> Following is an excerpt from the dump file.
> COPY compmstr (alienvendorcode, alienlinecode, alienpartnumber, jobber, list, da
> te, replacedbypart, specialmarkets, discount) FROM stdin;
> 001 66 16-4002 32.50 65.65 2003-05-26 00:00:00
> \N 0.00 0.00
> 001 66 16-4003 32.50 65.65 2003-05-26 00:00:00
> \N 0.00 0.00
> 001 66 16-4006 32.50 65.65 2003-05-26 00:00:00
> \N 0.00 0.00
> 001 66 16-4013 32.50 65.65 2003-05-26 00:00:00
> \N 0.00 0.00
> See what I mean? I am wondering if there is actually a new line character in the database or if the \N is
representinga NULL value?
The \N's represent nulls, yes. The question is why psql has a problem
with them. It should know that it's inside COPY data and not
misinterpret them as psql commands. This is not something that's
changed lately --- we've always handled NULLs like this --- so I'm
mystified why you are having a problem. Can you characterize the cases
in which psql gets confused?
regards, tom lane
