Re: Tuple data - Mailing list pgsql-hackers

From Hiroshi Inoue
Subject Re: Tuple data
Date
Msg-id 3A3D55ED.4D8CA2B9@tpf.co.jp
Whole thread Raw
In response to Tuple data  ("Michael Richards" <miker@interchange.ca>)
Responses Re: Tuple data  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Tuple data  ("Robert B. Easter" <reaster@comptechnews.com>)
List pgsql-hackers
Hannu Krosing wrote:
> 
> Tom Lane wrote:
> >
> >> ALTER ADD COLUMN doesn't touch any tuples, and you're right that it's
> > critically dependent on heap_getattr returning NULL when an attribute
> > beyond the number of attributes actually present in a tuple is accessed.
> > That's a fragile and unclean implementation IMHO --- see past traffic
> > on this list.
> 
> Short of redesigning the whole storage format I can see no better way to
> allow
> ALTER ADD COLUMN in any reasonable time. And I cna see no place where
> this is
> more "fragile and unclean implementation" than any other in postgres --
> OTOH it is quite hard for me to "see the past traffic on this list"  as
> my
> "PgSQL HACKERS" mail folder is too big for anything else then grep ;)
>

I don't remember the traffic either.
IIRC,I objected to Tom at this point in pgsql-bugs recently.
I think it's very important for dbms that ALTER ADD COLUMN
touches tuples as less as possible.

Regards.
Hiroshi Inoue


pgsql-hackers by date:

Previous
From: "Michael Richards"
Date:
Subject: Re: Attribute Alignment
Next
From: Hiroshi Inoue
Date:
Subject: Re: TOAST-table vacuuming (was Re: Idea for reducing planning time)