Our use case is that we want to copy the indexes from the parent table as
well, so we have to use (like ... including indexes).
On Thu, Oct 4, 2012 at 7:38 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> bryan(dot)love(at)iovation(dot)com writes:
> > After creating a table using LIKE and INHERITS, if you drop a column from
> > the parent table that existed prior to creation of the child table, the
> > column will not be dropped from the child table.
> This is not a bug. LIKE says the column isn't inherited, so it exists
> in the child independently of whether it exists in the parent.
> Or, if you want to add it up: the child starts out with one local
> definition of the column (from LIKE) and one inherited (from INHERITS).
> Dropping the column from the parent removes the latter, but you still
> have the former, so the column stays.
> > =# create table bar (like foo) inherits (foo);
> Just out of curiosity, is there any actual use-case for such a silly
> regards, tom lane
In response to
pgsql-bugs by date
|Next:||From: Bruce Momjian||Date: 2012-10-04 19:12:01|
|Subject: Re: BUG #7573: data loss in corner case using
|Previous:||From: Tom Lane||Date: 2012-10-04 14:38:35|
|Subject: Re: BUG #7583: Problem using INHERITS and LIKE|