From: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Don Baccus" <dhogaza(at)pacifier(dot)com>, "Zeugswetter Andreas SB" <ZeugswetterA(at)wien(dot)spardat(dot)at>, "The Hermit Hacker" <scrappy(at)hub(dot)org>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "PostgreSQL Development" <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | RE: AW: ALTER TABLE DROP COLUMN |
Date: | 2000-10-15 23:21:11 |
Message-ID: | EKEJJICOHDIEMGPNIFIJGEOJCIAA.Inoue@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
>
> "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> writes:
> > My trial implementation using physical/logical attribute numbers
> > isn't so clean as I expected. I'm inclined to restrict my change to
> > fix the TODO
> > * ALTER TABLE ADD COLUMN to inherited table put column in wrong place
> > though it would also introduce a backward compatibility.
>
> I'm confused --- how will that make things any simpler or cleaner?
> You still need physical/logical column numbering distinction in order
> to fix inherited ADD COLUMN, don't you?
>
Yes,the implementation would be almost same.
I've been busy for some time and wasn't able to follow
this thread. Don't people love 2x DROP COLUMN ?
I don't object to 2x DROP COLUMN if it could be
implemented properly though I don't want to implement
it myself. However I would strongly object to 2x ADD
COLUMN if such implementations are proposed.
Regards.
Hiroshi Inoue
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-10-15 23:24:36 | Re: Performance on inserts |
Previous Message | Bruce Momjian | 2000-10-15 23:20:35 | Re: Performance on inserts |