[snip]
> So (for instance) if you have 12 variable fields, you would 
> store 12 integers at the start of the record.

Additionally, you could implicitly size the integers from the properties
of the column.  A varchar(255) would only need an unsigned char to store
the offset, but a varchar(80000) would require an unsigned int.

Wed, 22 Jan 2003 16:22:51 -0800
"Dann Corbit" <DCorbit@connx.com>
Re: Terrible performance on wide selects 
Dann Corbit kirjutas N, 23.01.2003 kell 02:22:
> [snip]
> > So (for instance) if you have 12 variable fields, you would 
> > store 12 integers at the start of the record.
> 
> Additionally, you could implicitly size the integers from the properties
> of the column.  A varchar(255) would only need an unsigned char to store
> the offset, but a varchar(80000) would require an unsigned int.

I guess that the pointer could always be 16-bit, as the offset inside a
tuple will never be more (other issues constrain max page size to 32K)

varchar(80000) will use TOAST (another file) anyway, but this will be
hidden inside the field storage in the page)

> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
-- 
Hannu Krosing <hannu@tm.ee>

23 Jan 2003 19:42:26 +0200
Hannu Krosing <hannu@tm.ee>
Re: Terrible performance on wide selects