Re: [HACKERS] Arbitrary tuple size - Mailing list pgsql-hackers

From wieck@debis.com (Jan Wieck)
Subject Re: [HACKERS] Arbitrary tuple size
Date
Msg-id m112IgM-0003ktC@orion.SAPserv.Hamburg.dsh.de
Whole thread Raw
In response to Re: [HACKERS] Arbitrary tuple size  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] Arbitrary tuple size
Re: [HACKERS] Arbitrary tuple size
Re: [HACKERS] Arbitrary tuple size
Re: [HACKERS] Arbitrary tuple size
List pgsql-hackers
Tom Lane wrote:

>
> wieck@debis.com (Jan Wieck) writes:
> > Bruce Momjian wrote:
> >> I agree this is the way to go.  There is nothing I can think of that is
> >> limited to how large a tuple can be.
>
> >     Outch - I can.
>
> >     Having  an  index  on a varlen field that now doesn't fit any
> >     more into an index block. Wouldn't this cause problems?
>
> Aren't index tuples still tuples?  Can't they be split just like
> regular tuples?

    Don't know, maybe.

    While  looking  for  some  places  where  tuple data might be
    accessed directly inside of the  buffers  I've  searched  for
    WriteBuffer() and friends. These are mostly used in the index
    access methods and some other places where I  expected  them,
    so  index  AM's  have  at  least to be carefully visited when
    implementing tuple split.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#========================================= wieck@debis.com (Jan Wieck) #

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Arbitrary tuple size
Next
From: Leon
Date:
Subject: Re: [HACKERS] Fwd: Joins and links