Re: more information on OSX pg_dump problem - Mailing list pgsql-bugs

From Theodore Petrosky
Subject Re: more information on OSX pg_dump problem
Date
Msg-id 20021125004125.67637.qmail@web41009.mail.yahoo.com
Whole thread Raw
In response to Re: more information on OSX pg_dump problem  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tom,

I have checked the dump file with hexedit and find
that the lines end with '0A' hex. Only one character.

What is strange is that I have multiple tables, some
of them are going in fine.

Ted


-- Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Theodore Petrosky <tedpet5@yahoo.com> writes:
> > COPY "fcopenjobs"  FROM stdin;
> > If I copy and paste the lines (from the dump file)
> > into psql one by one, it will input fine. However,
> If
> > I cut and paste more that two lines, the input
> fails.
>
> I'm wondering about newline representations, myself.
>  Is it possible
> that you've got CR or CR/LF newlines, and not LF
> newlines, in the
> dump file?  COPY presently only likes LF
> (Unix-style) newlines.
>
>             regards, tom lane


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus – Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: more information on OSX pg_dump problem
Next
From: pgsql-bugs@postgresql.org
Date:
Subject: Bug #823: upper() does not handle å, ä and ö correctly.