Re: COPY x FROM STDIN escape handlers

From: Marc Lavergne <mlavergne-pub(at)richlava(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: COPY x FROM STDIN escape handlers
Date: 2002-07-15 18:14:59
Message-ID: 3D331123.1060709@richlava.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I see the problem now. It was my file parser that was escaping the value
then passing it to PQescapeString which resulted in \\n instead of \n.
Guess I was on a wild goose chase. I guess PQescapeString() and
PQputline() are mutally exclusive ... my bad!

Thanks,

Marc L.

Tom Lane wrote:
> Marc Lavergne <mlavergne-pub(at)richlava(dot)com> writes:
>
>>Just to give a little background, using pgdump in "default" mode creates
>>a dump file that includes inline newlines and tabs.
>
>
> How old a PG release are you using? COPY has quoted special characters
> properly for a long time.
>
> regards, tom lane
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-07-15 20:46:44 HeapTuple header changes cause core dumps in CVS tip
Previous Message Sergio A. Kessler 2002-07-15 17:45:40 Re: More DROP COLUMN