From: | Hannu Krosing <hannu(at)tm(dot)ee> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Michael Richards <miker(at)interchange(dot)ca>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Tuple data |
Date: | 2000-12-17 22:27:05 |
Message-ID: | 3A3D3DB9.CBC8D76E@tm.ee |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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 ;)
The notion that anything not stored is NULL seems so natural to me that
it
is very hard to find any substantial flaw or fragility with it.
--------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-12-17 22:45:46 | Re: Attribute Alignment |
Previous Message | Oleg Bartunov | 2000-12-17 21:08:10 | Who is a maintainer of GiST code ? |