I think we may be using too many words in this discussion.
Perhaps there is a message in this thread that I have not seen.
Miroslav, have you tested for carriage returns in your data, and if so, what
did you find?
If that is the problem, the carriage returns are easily edited out, and
speculation about the cause may use more time than it is worth...
If that is not the problem, we definitely have something weird.
The original error message shows the problem occurring at the first line of
your data. Perhaps you could pipe the first few lines through some utility
that shows nonprinting characters (like "vis -lw"), and see what that shows?
----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Miroslav Koncar" <miroslav.koncar@etk.ericsson.se>
Cc: <pgsql-general@postgresql.org>
Sent: Friday, August 24, 2001 8:13 AM
Subject: Re: [GENERAL] problems transfering databases
> Miroslav Koncar <miroslav.koncar@etk.ericsson.se> writes:
> > The only thing I can think of is the PostgreSQL versions. My collegue is
> > using 7.0.3, and I use 7.1.2. Comments?
>
> That wouldn't produce a carriage-return problem.
>
> It's possible that we're barking up the wrong tree, and that the issue
> is not carriage returns but something else --- I just jumped to that
> conclusion based on the way you presented the error message. But maybe
> the error message was mangled because you were sloppy about cutting-and-
> pasting it into your email, or some such. Have you looked at the data
> to try to narrow down exactly which line is being rejected?
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>
>
