Re: reading row in backend - Mailing list pgsql-hackers

From Tom Lane
Subject Re: reading row in backend
Date
Msg-id 2837.958437843@sss.pgh.pa.us
Whole thread Raw
In response to Re: reading row in backend  (Patrick Welche <prlw1@newn.cam.ac.uk>)
Responses Re: reading row in backend  (Patrick Welche <prlw1@newn.cam.ac.uk>)
List pgsql-hackers
Patrick Welche <prlw1@newn.cam.ac.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...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Proposal: replace no-overwrite with Berkeley DB
Next
From: "Michael A. Olson"
Date:
Subject: Re: Berkeley DB license terms (was Re: Proposal...)