Re: BETWEEN Node & DROP COLUMN - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: BETWEEN Node & DROP COLUMN
Date
Msg-id GNELIHDDFBOCMGBFGEFOGEPOCCAA.chriskl@familyhealth.com.au
Whole thread Raw
In response to Re: BETWEEN Node & DROP COLUMN  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
List pgsql-hackers
> > It merrily renames the column in the child table (I tried it).  When
> > SELECTing the parent, bogus data appears.  Looks like a bug to me.
> > Maybe the ALTER TABLE ...  RENAME COLUMN code should check for inherited
> > columns before renaming them.
>
> Hmmm...so how does one check if one is a child in an inheritance
> hierarchy?

Actually, more specifically, how does one check that the column being
dropped or renamed appears in none of one's parent tables?

I notice there's no find_all_ancestors() function...

Chris





pgsql-hackers by date:

Previous
From: "Christopher Kings-Lynne"
Date:
Subject: DROP COLUMN Progress
Next
From: "J. R. Nield"
Date:
Subject: Re: Issues Outstanding for Point In Time Recovery (PITR)