From: | Christof Petig <christof(dot)petig(at)wtal(dot)de> |
---|---|
To: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Volunteer: Large Tuples / Tuple chaining |
Date: | 1999-12-13 21:59:27 |
Message-ID: | 38556C3E.B49841E0@wtal.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hiroshi Inoue wrote:
>
> Will you put a long tuple into a long logical page(continued multiple
> phisical(?) pages) ?
> I'm suspicious about the way that allows non-page-formatted page.
>
> Anyway it would need a big change around bufmgr/smgr etc.
> Could someone estimate the influence/danger before going forward ?
>
I planned to use as many of PostgreSQL data structures unaltered as
possible. Storing one Tuple in multiple Items should not pose too much
danger on bufmgr and smgr unless they access tuple internals. (I didn't
check that yet). This would mean that on disk Items do no longer
correspond to Tuples. (Some of them might form one tuple).
I dropped the plan of Unformatted pages very soon. But the issue of
tuple in-memory-storage remains (I don't know the internals of
allocating/freeing, yet).
Christof
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1999-12-13 22:24:38 | Re: [HACKERS] "ExecInitIndexScan: both left and right..." meaning? |
Previous Message | Christof Petig | 1999-12-13 21:50:52 | Re: [HACKERS] LONG |