Skip site navigation (1) Skip section navigation (2)

Re: more information on OSX pg_dump problem

From: Theodore Petrosky <tedpet5(at)yahoo(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: more information on OSX pg_dump problem
Date: 2002-11-25 00:41:25
Message-ID: (view raw or whole thread)
Lists: pgsql-bugs

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.


-- Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Theodore Petrosky <tedpet5(at)yahoo(dot)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.

In response to

pgsql-bugs by date

Next:From: paolo mancaDate: 2002-11-25 11:10:56
Subject: BUG
Previous:From: Tom LaneDate: 2002-11-24 22:36:34
Subject: Re: more information on OSX pg_dump problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group