| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | Michael Richards <miker(at)interchange(dot)ca> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Tuple data |
| Date: | 2000-12-16 20:09:27 |
| Message-ID: | 3A3BCBF7.470B41EB@tm.ee |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Richards wrote:
>
> Hi.
>
> I've still got something I can't seem to get. In my test cases with simple
> tables the first uint16 of tuple data after the header contained the length
> of the tuple. In this case I can't seem to figure out what the value F24D
> stands for when I'd expect it's length to be 0800.
I'm not sure, but you may see some part of the NULL bitmap.
IIRC it started at a quite illogical place, is suspect it was at byte 31
but
it still reserved 4bytes for each 32 fields after byte 32
> The first tuple in my table has:
...
> Bitmap: 3F00 0000 00F2
> Attributes: 7
you should have only 4 bytes of bitmap for 7 real attributes
> Data Offset: 36
thats' right 32+4
----------
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Richards | 2000-12-16 20:14:29 | Re: Tuple data |
| Previous Message | Tom Lane | 2000-12-16 19:57:03 | Re: Tuple data |