Re: pgsql: Teach expr_is_nonnullable() to handle more expression types

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgsql: Teach expr_is_nonnullable() to handle more expression types
Date: 2026-10-10 02:01:32
Message-ID: CAMbWs49b6UzqYSN1gC4nCkRSHdJD+F5hQuadF1RueDdVhgHN1g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Thu, Oct 8, 2026 at 10:49 PM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> But I'd be inclined to use a conditional rule only if
> we can base it on information that we already have cached in some
> planner data structure, and not if we'd have to look it up in the
> catalog.

We don't have that cached, so I've pushed a fix that just removes the
case. It also moves the relkind test ahead of has_subclass().

- Richard

In response to

Browse pgsql-committers by date

  From Date Subject
Previous Message Richard Guo 2026-10-10 01:53:48 pgsql: Fix expr_is_nonnullable() for IS DISTINCT FROM

Browse pgsql-hackers by date

  From Date Subject
Previous Message Tom Lane 2026-10-10 01:19:37 Re: docs: Table 9.46. UUID Extraction Functions