> That seems right, but the problem I have with it is that the resulting
> state of c.f1 is attisinherited = 1. This means that you cannot drop
> c.f1. It seems to me that we should have this behavior:
Has anyone given much thought as to perhaps we could just drop multiple
inheritance from Postgres? There are people using single inheritance - but
how many actually use multiple inheritance? If we dumped it we could use
the proposed all-child-tables-in-one-relation idea, and everything would
become very easy...
Chris