| From: | Miroslav Koncar <miroslav(dot)koncar(at)etk(dot)ericsson(dot)se> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: problems transfering databases |
| Date: | 2001-08-24 13:45:36 |
| Message-ID: | 3B865A7F.5154EC93@etk.ericsson.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-odbc |
Hello Tom,
problem solved! The error was caused by interpreting \N as a special
character, and not what postgreSQL wants it to be. I've solved it by
replaceing all \N with \\N in a texteditor, which made the shell not to
interpret the character.
Thanks for your suggestions and help.
Miroslav
Tom Lane wrote:
> Miroslav Koncar <miroslav(dot)koncar(at)etk(dot)ericsson(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-08-24 13:50:52 | Re: BIGINT datatype and Indexes Failure |
| Previous Message | Tom Lane | 2001-08-24 13:41:30 | Re: |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Eckermann | 2001-08-24 14:14:19 | Re: problems transfering databases |
| Previous Message | Tom Lane | 2001-08-24 13:13:25 | Re: problems transfering databases |