Horton

Re: AW: ALTER TABLE DROP COLUMN

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Hiroshi Inoue" <Inoue@tpf.co.jp>
Cc: "Don Baccus" <dhogaza@pacifier.com>, "Zeugswetter Andreas SB" <ZeugswetterA@wien.spardat.at>, "The Hermit Hacker" <scrappy@hub.org>, "Bruce Momjian" <pgman@candle.pha.pa.us>, "PostgreSQL Development" <pgsql-hackers@postgreSQL.org>
Date: 2000-10-15T15:57:32Z
Lists: pgsql-hackers 
"Hiroshi Inoue" <Inoue@tpf.co.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?

			regards, tom lane