| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | prlw1(at)cam(dot)ac(dot)uk |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: reading row in backend |
| Date: | 2000-05-15 23:22:30 |
| Message-ID: | 29282.958432950@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:
>> Um ... doesn't that line number in the COPY source data help any?
> Unfortunately not - in fact the 2nd large tuple allegedly has a smaller
> line number than the first :(
Hmm, are you claiming that COPY is reporting a bogus line number?
If so, that needs to be looked into.
> Am I barking up the wrong tree if I think that the HeapTuple contains the
> actual data? The first number in it would the primary key...
Type HeapTuple is a pointer to a HeapTupleData, which is just
administrative overhead. The t_data field of the HeapTupleData
points at the actual tuple (a HeapTupleHeaderData followed by
null-values bitmap and then the user data). See include/access/htup.h
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Patrick Welche | 2000-05-15 23:37:02 | Re: reading row in backend |
| Previous Message | Patrick Welche | 2000-05-15 23:09:00 | Re: reading row in backend |