Re: [HACKERS] COPY problems with psql / libpq

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Oliver Elphick <olly(at)lfix(dot)co(dot)uk>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] COPY problems with psql / libpq
Date: 2000-01-20 22:35:45
Message-ID: 25103.948407745@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>> : psql.c doesn't appear to cope correctly with quoted newlines in COPY data;

> What's a quoted newline?
> a) "<newline>"
> b) "\n"
> c) \<newline>

(c). That's how a newline appearing in the data is supposed to be
represented. IIRC, I was worried that if the \ falls at the end of
a bufferload and the newline at the start of the next, psql and/or
libpq would fail to recognize the pattern; if so, they'd probably
think the newline is a record boundary.

Patrick could be falling victim to this, but Oliver sez he has no
newlines in his data, so there's at least one other problem.

> that would in any case still point to a problem elsewhere. Gotta pass the
> buck to libpq ...

Could be. I think Alfred is on the hook here...

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-01-20 22:42:39 Re: [HACKERS] timezone problem?
Previous Message Bruce Momjian 2000-01-20 22:19:53 New INSTALL text file