Re: dropping column prevented due to inherited index - Mailing list pgsql-hackers

From Amit Langote
Subject Re: dropping column prevented due to inherited index
Date
Msg-id CA+HiwqEn+LAmTNN7oJC4a05N0ai6ymxxwxAKpAT=_1P_ZJdkbQ@mail.gmail.com
Whole thread Raw
In response to Re: dropping column prevented due to inherited index  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: dropping column prevented due to inherited index  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Tue, Oct 8, 2019 at 6:15 PM Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
> Apologies for not helping much here; I'm on vacation for a couple of
> weeks.

No worries, please take your time.

> On 2019-Oct-08, Amit Langote wrote:
>
> > I couldn't imagine how that trick could be implemented for this case. :(
>
> Can't we pass around an ObjectAddresses pointer to which each recursion
> level adds the object(s) it wants to delete, and in the outermost level
> we drop everything in it?  I vaguely recall we implemented something
> like that somewhere within the past year, but all I can find is
> 20bef2c3110a.

I thought about doing something like that, but wasn't sure if
introducing that much complexity is warranted.

Thanks,
Amit



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: dropping column prevented due to inherited index
Next
From: Ants Aasma
Date:
Subject: Re: Transparent Data Encryption (TDE) and encrypted files