Re: Assert failure of the cross-check for nullingrels

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Assert failure of the cross-check for nullingrels
Date: 2023-03-13 09:44:18
Message-ID: CAMbWs489MSrXdBDFis-KDKDBzZ4xg_UWqUrbR+9agYdxgNBtrw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 13, 2023 at 5:03 PM Richard Guo <guofenglinux(at)gmail(dot)com> wrote:

> Back to the original issue, if a join has more than one quals, actually
> we treat them as a whole when we check if identity 3 applies as well as
> when we adjust them to be suitable for commutation according to identity
> 3. So when we check if a qual is computable at a given level, I think
> we should also consider the join's quals as a whole. I'm thinking that
> we use a 'group' notion for RestrictInfos and then use the clause_relids
> of the 'group' in clause_is_computable_at. Does this make sense?
>

I'm imagining something like attached (no comments and test cases yet).

Thanks
Richard

Attachment Content-Type Size
v1-0001-Draft-group-RestrictInfos.patch application/octet-stream 4.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Drouvot, Bertrand 2023-03-13 09:54:16 Re: [BUG] pg_stat_statements and extended query protocol
Previous Message houzj.fnst@fujitsu.com 2023-03-13 09:42:47 RE: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher