Re: BUG #16276: Server crash on an invalid attempt to attach a partition to an index

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: exclusion(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Subject: Re: BUG #16276: Server crash on an invalid attempt to attach a partition to an index
Date: 2020-02-27 12:49:52
Message-ID: 20200227124952.GC403330@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Feb 27, 2020 at 05:14:28PM +0900, Amit Langote wrote:
> Simply dropping the culprit assertion might be enough for
> back-branches, but it seems misleading to silently ignore the bound
> IMO.

Yeah, I have been considering this option, still I am hesitating about
what to do on HEAD. My own take would be to fix this issue on all
branches by removing the assertion, but I think that we should wait
first a couple of days to see if Alvaro can comment on this issue.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexey Ermakov 2020-02-27 14:07:51 Re: BUG #16280: dead tuples (probably) effect plan and query performance
Previous Message PG Bug reporting form 2020-02-27 11:28:11 BUG #16280: dead tuples (probably) effect plan and query performance