Re: BUG #18171: Dropping an index on a partitioned table drops all child indices even with a restrict

I first observed this on a production system running 15.3. I've re-run the
tests on 15.4 locally and produced the same result.

I realize in my original email that I didn't put restrict, so I've added
restrict and confirmed that the child indices are dropped.

postgres=# drop index parent_id_index restrict;
DROP INDEX

Would you consider this an unimplemented feature then, instead of a bug? If
so, i'll repost in general.

On Thu, 26 Oct 2023 at 11:33, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:

> On Thu, Oct 26, 2023 at 8:23 AM PG Bug reporting form <
> noreply(at)postgresql(dot)org> wrote:
>
>> The following bug has been logged on the website:
>>
>> Bug reference: 18171
>> Logged by: Nick Dujay
>> Email address: nickdujay(at)gmail(dot)com
>> PostgreSQL version: 12.8
>> Operating system: macOS
>> Description:
>>
>>
> Your examples below don't seem to match up with the subject line. And you
> are using a two year old unsupported minor release of v12. And the
> examples below don't indicate any kind of bug. If this really is a bug
> report you should demonstrate that more succinctly, and upgrade to the
> current supported release to see whether it has already been fixed.
>
> If you are looking for general help on how to do things, or just want to
> voice your disappointment regarding some unimplemented feature in v12, the
> -general mailing list is the appropriate forum.
>
> David J.
>
>