Re: AW: ALTER TABLE DROP COLUMN - Mailing list pgsql-hackers

From Tom Lane
Subject Re: AW: ALTER TABLE DROP COLUMN
Date
Msg-id 4908.971625452@sss.pgh.pa.us
Whole thread Raw
In response to RE: AW: ALTER TABLE DROP COLUMN  ("Hiroshi Inoue" <Inoue@tpf.co.jp>)
Responses RE: AW: ALTER TABLE DROP COLUMN  ("Hiroshi Inoue" <Inoue@tpf.co.jp>)
List 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


pgsql-hackers by date:

Previous
From: KuroiNeko
Date:
Subject: select oid .... for update ....
Next
From: Stephan Szabo
Date:
Subject: Re: select oid .... for update ....