Re: Wrong result for whole-row IS NOT NULL with dropped columns

From: Sho Ito <i(dot)sho(dot)0628(at)gmail(dot)com>
To: Matheus Alcantara <matheusssilv97(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Wrong result for whole-row IS NOT NULL with dropped columns
Date: 2026-10-22 14:03:33
Message-ID: CAG7L5+4isfV2ua2+7k17fR=sscNP_BmHRXWeCFEK-zEA_20meA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 21, 2026 at 12:05 AM Matheus Alcantara <matheusssilv97(at)gmail(dot)com>
wrote:

> The attached patch fixes this by looking up the rowtype's tuple
> descriptor when simplifying a NullTest on a RowExpr of a named
> composite type and skipping the fields that correspond to dropped
> columns, which matches what the executor does.

Hi Matheus,

I reviewed v1 with assertions enabled,
and found no blocking issue in the changes.

Thanks,
Sho Ito

--
=======================================
*Sho Ito (Sean)*

E-mail: i(dot)sho(dot)0628(at)gmail(dot)com
LinkedIn: *https://www.linkedin.com/in/sho-ito-0628/
<https://www.linkedin.com/in/sho-ito-0628/>*
GitHub: https://github.com/sean0628/
=======================================

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Sho Ito 2026-10-22 14:09:22 Re: [PATCH] Fix leaked hash scans in pg_listening_channels()
Previous Message Greg Burd 2026-10-22 13:57:03 Re: [PATCH]Fix planner's strictness check for JsonExpr