Re: Assert failure of the cross-check for nullingrels

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Richard Guo <guofenglinux(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Assert failure of the cross-check for nullingrels
Date: 2023-06-06 20:11:32
Message-ID: 20230606201132.i3xjwpsg36p6tii7@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2023-May-21, Tom Lane wrote:

> Since we're hard up against the beta1 wrap deadline, I went ahead
> and pushed the v5 patch. I doubt that it's perfect yet, but it's
> a small change and demonstrably fixes the cases we know about.
>
> As I said in the commit message, the main knock I'd lay on v5
> is "why not use required_relids all the time?".

So, is this done? I see that you made other commits fixing related code
several days after this email, but none seems to match the changes you
posted in this patch; and also it's not clear to me that there's any
test case where this patch is expected to change behavior. (So there's
also a question of whether this is a bug fix or rather some icying on
cake.)

--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2023-06-06 20:14:41 Re: Let's make PostgreSQL multi-threaded
Previous Message Jonathan S. Katz 2023-06-06 20:00:55 Re: Order changes in PG16 since ICU introduction