From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Hannu Krosing <hannu(at)tm(dot)ee> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: DROP COLUMN misbehaviour with multiple inheritance |
Date: | 2002-09-12 14:14:46 |
Message-ID: | 6917.1031840086@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Hannu Krosing <hannu(at)tm(dot)ee> writes:
> I've come upon a misbehaviour of drop column, where drop column
> unconditionally drops inherited column from child tables.
> What it should do is to check if the same column is not inherited from
> other parents and drop it only when it is not
Hm. Seems like attisinherited should have been a count, not a boolean.
Is anyone sufficiently excited about this issue to force an initdb to
fix it?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-09-12 14:31:00 | Re: OPAQUE and 7.2-7.3 upgrade |
Previous Message | Tom Lane | 2002-09-12 13:07:20 | Re: 7.3beta and ecpg |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-09-12 14:35:49 | Re: Earth Distance patch |
Previous Message | Bruno Wolff III | 2002-09-12 13:17:16 | Earth Distance patch |