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

From Chris Bitmead
Subject Re: ALTER TABLE DROP COLUMN
Date
Msg-id 39457D58.F342701A@nimrod.itg.telecom.com.au
Whole thread Raw
In response to RE: ALTER TABLE DROP COLUMN  ("Hiroshi Inoue" <Inoue@tpf.co.jp>)
Responses RE: ALTER TABLE DROP COLUMN
List pgsql-hackers
Hiroshi Inoue wrote:

> I don't understand inheritance well. In the near future wouldn't the
> implementation require e.g. attid which is common to all children
> of a parent and is never changed ? If so,we would need the third
> attid field which is irrevalent to physical/logical position. If not,
> physical column number would be sufficient .

We only need something like a unique attid of course if we support
column renaming in child tables. Otherwise the attname is sufficient to
match up child-parent columns.

If/when we support renaming, probably a parent_column_oid in
pg_attribute might be one way to go.

Your idea seems fine Tom.


pgsql-hackers by date:

Previous
From: Chris Bitmead
Date:
Subject: Re: ALTER TABLE DROP COLUMN
Next
From: "valter m"
Date:
Subject: how an app can know when a table is altered ?