From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | Hannu Krosing <hannu(at)tm(dot)ee> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Richards <miker(at)interchange(dot)ca>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Tuple data |
Date: | 2000-12-18 00:10:21 |
Message-ID: | 3A3D55ED.4D8CA2B9@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2000-12-18 00:41:39 | Re: TOAST-table vacuuming (was Re: Idea for reducing planning time) |
Previous Message | Michael Richards | 2000-12-17 23:03:34 | Re: Attribute Alignment |