RE: [HACKERS] Volunteer: Large Tuples / Tuple chaining

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Christof Petig" <christof(dot)petig(at)wtal(dot)de>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: RE: [HACKERS] Volunteer: Large Tuples / Tuple chaining
Date: 1999-12-14 08:58:57
Message-ID: 001801bf4611$74dd1ee0$2801007e@cadzone.tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: christof(at)to(dot)wtal(dot)de [mailto:christof(at)to(dot)wtal(dot)de]On Behalf Of
> Christof Petig
>
> 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).
>

Hmm,we have discussed about LONG.
Change by LONG is transparent to users and would resolve
the big tuple problem mostly.
I'm suspicious that tuple chaining is worth the work now.

At least a consensus is needed before going,I think.
Bad design would only introduce a confusion.

Regards.

Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas SB 1999-12-14 09:39:29 Re: [HACKERS] Create Group
Previous Message Tatsuo Ishii 1999-12-14 08:54:54 Questionable codes