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

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: nickdujay(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18171: Dropping an index on a partitioned table drops all child indices even with a restrict
Date: 2023-10-26 15:33:10
Message-ID: CAKFQuwZsy7+JNj-cqw7W3rtkewTrENhEzX0-yZfmQx+eVdiFXA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Nicholas Dujay 2023-10-26 16:17:07 Re: BUG #18171: Dropping an index on a partitioned table drops all child indices even with a restrict
Previous Message Vik Fearing 2023-10-26 15:21:07 Re: BUG #18170: Unexpected error: no relation entry for relid 3