RE: [HACKERS] Volunteer: Large Tuples / Tuple chaining - Mailing list pgsql-hackers

From Hiroshi Inoue
Subject RE: [HACKERS] Volunteer: Large Tuples / Tuple chaining
Date
Msg-id 001801bf4611$74dd1ee0$2801007e@cadzone.tpf.co.jp
Whole thread Raw
In response to Re: [HACKERS] Volunteer: Large Tuples / Tuple chaining  (Christof Petig <christof.petig@wtal.de>)
Responses Re: [HACKERS] Volunteer: Large Tuples / Tuple chaining
List pgsql-hackers
> -----Original Message-----
> From: christof@to.wtal.de [mailto:christof@to.wtal.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@tpf.co.jp 


pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Questionable codes
Next
From: Zeugswetter Andreas SB
Date:
Subject: Re: [HACKERS] Create Group