Re: reading row in backend

From: Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: reading row in backend
Date: 2000-05-16 09:42:05
Message-ID: 20000516104205.A22959@quartz.newn.cam.ac.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, May 15, 2000 at 08:44:03PM -0400, Tom Lane wrote:
> Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk> writes:
> >> Hmm, are you claiming that COPY is reporting a bogus line number?
> >> If so, that needs to be looked into.
>
> > Yup:
>
> > ERROR: copy: line 57552, Tuple is too big: size 8152, max size 8140
> > PQendcopy: resetting connection
> > ERROR: copy: line 26714, Tuple is too big: size 8164, max size 8140
> > PQendcopy: resetting connection
>
> > % wc /home/prlw1/db.out
> > 3631449 19833180 186847533 /home/prlw1/db.out
>
> > and the second line is in a table that is over half way through the file.
>
> Looks reasonable enough to me. The line numbers are within the data
> being fed to that copy command --- copy has no way to know that it's
> part of some larger script...

Ah! Thank you! So it's 57552 rows down from "COPY" !

OK

Cheers,

Patrick

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message The Hermit Hacker 2000-05-16 11:54:27 Re: Problems with the new Majordomo 2.
Previous Message Tatsuo Ishii 2000-05-16 09:30:48 RE: PostgreSQL and Unicode