Re: [BUG?] strange behavior in ALTER TABLE ... RENAME TO on inherited columns

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thom Brown <thombrown(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [BUG?] strange behavior in ALTER TABLE ... RENAME TO on inherited columns
Date: 2009-11-04 14:41:31
Message-ID: 15400.1257345691@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thom Brown <thombrown(at)gmail(dot)com> writes:
> 2009/11/4 Alvaro Herrera <alvherre(at)commandprompt(dot)com>:
>> KaiGai Kohei wrote:
>>> I think we should not allow to rename a column with attinhcount > 1.

>> I think we should fix ALTER TABLE to cope with multiple inheritance.

> I'd be interested to see how this should work.

Yeah. I don't think a "fix" is possible, because there is no
non-astonishing way for it to behave. I think KaiGai is right that
forbidding the rename is the best solution.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-11-04 14:44:10 Re: PL/Python array support
Previous Message Bernd Helmle 2009-11-04 14:39:56 ALTER TABLE...ALTER COLUMN vs inheritance