Re: BUG #18171: Dropping an index on a partitioned table drops all child indices even with a restrict - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #18171: Dropping an index on a partitioned table drops all child indices even with a restrict
Date
Msg-id CAKFQuwZsy7+JNj-cqw7W3rtkewTrENhEzX0-yZfmQx+eVdiFXA@mail.gmail.com
Whole thread Raw
In response to BUG #18171: Dropping an index on a partitioned table drops all child indices even with a restrict  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #18171: Dropping an index on a partitioned table drops all child indices even with a restrict  (Nicholas Dujay <nickdujay@gmail.com>)
List pgsql-bugs
On Thu, Oct 26, 2023 at 8:23 AM PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      18171
Logged by:          Nick Dujay
Email address:      nickdujay@gmail.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.

pgsql-bugs by date:

Previous
From: Vik Fearing
Date:
Subject: Re: BUG #18170: Unexpected error: no relation entry for relid 3
Next
From: Nicholas Dujay
Date:
Subject: Re: BUG #18171: Dropping an index on a partitioned table drops all child indices even with a restrict