Re: Syntax error in a large COPY - Mailing list pgsql-general

From Scott Marlowe
Subject Re: Syntax error in a large COPY
Date
Msg-id dcc563d10711061313o24ce5bc4k60ae9eb8cdb90f4d@mail.gmail.com
Whole thread Raw
In response to Re: Syntax error in a large COPY  (Reg Me Please <regmeplease@gmail.com>)
Responses Re: Syntax error in a large COPY  (Reg Me Please <regmeplease@gmail.com>)
List pgsql-general
On 11/6/07, Reg Me Please <regmeplease@gmail.com> wrote:
> Il Tuesday 06 November 2007 19:43:38 Scott Marlowe ha scritto:
> > On 11/6/07, Reg Me Please <regmeplease@gmail.com> wrote:
> > > That seems not to be the case.
> > > The last line has a \. by its own and the last but one is
> > > well formed.
> >
> > (Please don't top post...)
> >
> > Got a self contained test case you can post?
>
> Back to the original topic ...
>
> I'm trying to understand what and where.
> The point is that I have this 29M+ lines script telling me there's a problem
> somewhere.
>
> A self contained test, at the moment, would be that long!
>
> I'm considering a "branch and bound" approach ... but it'd be quite long
> and tedious as the program generating the script has not been written
> to do such things.

Split it in half, with the appropriate sql on each end so the data
still works, and see which half causes a problem.  Keep splitting the
one that causes a problem in half until you have a small one with the
problem still.

I'm guessing the problem will become obvious then.

pgsql-general by date:

Previous
From: Rainer Bauer
Date:
Subject: Re: Npsql is much faster than ODBC ?
Next
From: Reg Me Please
Date:
Subject: Re: Syntax error in a large COPY