| From: | darrenk(at)insightdist(dot)com (Darren King) |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] varchar/char size |
| Date: | 1998-01-09 14:43:52 |
| Message-ID: | 9801091443.AA42084@ceodev |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> A related question: Is it possible to store tuples over more than one
> block? Would it be possible to split a big TEXT into multiple blocks?
>
Possible, but would cut the access speed to (1 / # blocks), no?
There is a var in the tuple header, t_chain, 6.2.1 that has since been
removed for 6.3. I think its original purpose was with time-travel,
_but_, if we go with a ROWID instead of an oid in the future, this could
be put back in the header and would be the actual address of the next
block in the chain.
Oracle has this concept of chained rows. It is how they implement all
of their LONG* types and also handle rows of normal types that are
larger than the block size.
darrenk
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas G. Lockhart | 1998-01-09 14:50:42 | Re: [HACKERS] varchar/char size |
| Previous Message | Mattias Kregert | 1998-01-09 13:26:43 | Re: [HACKERS] varchar/char size |