| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
| Cc: | Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: dropping column prevented due to inherited index |
| Date: | 2019-10-08 09:15:05 |
| Message-ID: | 20191008091505.GA15289@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Apologies for not helping much here; I'm on vacation for a couple of
weeks.
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.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2019-10-08 09:25:05 | Re: dropping column prevented due to inherited index |
| Previous Message | Peter Eisentraut | 2019-10-08 08:55:01 | Re: Remove some code for old unsupported versions of MSVC |