Re: pgsql 7.4.1 copy - end-of-copy marker corrupt - Mailing list pgsql-general

From Martijn van Oosterhout
Subject Re: pgsql 7.4.1 copy - end-of-copy marker corrupt
Date
Msg-id 20040206065210.GC28648@svana.org
Whole thread Raw
In response to Re: pgsql 7.4.1 copy - end-of-copy marker corrupt  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql 7.4.1 copy - end-of-copy marker corrupt  (Jenny Zhang <jenny@osdl.org>)
List pgsql-general
On Fri, Feb 06, 2004 at 01:11:24AM -0500, Tom Lane wrote:
> Jenny Zhang <jenny@osdl.org> writes:
> >  ERROR:  end-of-copy marker corrupt
> > CONTEXT:  COPY author, line 49: "49\aoD{\BABABABABARENG
> > \t5p.\19840426"
>
> > and this is the line in the data file it complains:
> > ===
> > 49\aoD{\BABABABABARENG
> > \t5p.\19840426\.XfqWM+Ke,8+Ae-9PWPn)}#6eVa_Qu ...
>                 ^^
>
> It doesn't like the "\.", with good reason I should think.  Are you sure
> 7.3 would take this file?
>
> Anyway, either double or remove that backslash, depending on what you
> want.

Umm, the copy is using the escape character as column seperator. I wonder if
we should catch and warn for that.

I don't think there is a sensible way that can actually work.

--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> (... have gone from d-i being barely usable even by its developers
> anywhere, to being about 20% done. Sweet. And the last 80% usually takes
> 20% of the time, too, right?) -- Anthony Towns, debian-devel-announce

Attachment

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql 7.4.1 copy - end-of-copy marker corrupt
Next
From: Peter Eisentraut
Date:
Subject: Upcoming events: Chemnitzer Linux-Tag