Re: pgsql 7.4.1 copy - end-of-copy marker corrupt

From: Jenny Zhang <jenny(at)osdl(dot)org>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: pgsql 7.4.1 copy - end-of-copy marker corrupt
Date: 2004-02-06 18:34:20
Message-ID: 1076092460.2096.13.camel@ibm-a.pdx.osdl.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, 2004-02-05 at 22:52, Martijn van Oosterhout wrote:
> On Fri, Feb 06, 2004 at 01:11:24AM -0500, Tom Lane wrote:
> > Jenny Zhang <jenny(at)osdl(dot)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.

Using \ as delimiter is a bad choice. But it did work under 7.3.3.
It would be nice to have an error message for it.

Thanks,
Jenny

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Stephan Szabo 2004-02-06 18:58:12 Re: Indexes and sorting
Previous Message Wei Wang 2004-02-06 18:21:04 Re: Run 2 versions of Postgresql on one machine?