| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: reading row in backend |
| Date: | 2000-05-16 00:44:03 |
| Message-ID: | 2837.958437843@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael A. Olson | 2000-05-16 00:44:35 | Re: Berkeley DB license terms (was Re: Proposal...) |
| Previous Message | Bruce Momjian | 2000-05-16 00:27:49 | Re: Proposal: replace no-overwrite with Berkeley DB |