Re: expand virtual generated columns in get_relation_constraints() - Mailing list pgsql-hackers

From Richard Guo
Subject Re: expand virtual generated columns in get_relation_constraints()
Date
Msg-id CAMbWs4-fbJbX_zwOsbRs0TVRF_BP6Sb4ZT3QC4OhearYBHamdw@mail.gmail.com
Whole thread Raw
In response to expand virtual generated columns in get_relation_constraints()  (Peter Eisentraut <peter@eisentraut.org>)
List pgsql-hackers
On Wed, Sep 3, 2025 at 11:05 PM Peter Eisentraut <peter@eisentraut.org> wrote:
> We (I) missed expanding virtual generated columns in
> get_relation_constraints() in plancat.c.  That way, some opportunities
> for constraint exclusion will be missed if a constraint contains virtual
> generated columns, as can be shown in the attached test case (thanks to
> Richard Guo).  Simple fix attached.

I'm afraid this fix isn't thorough: it covers only CHECK constraints
but not NOT NULL or partitioning constraints.  For example,

create table vt (a int, b int generated always as (a * 2) virtual not null);
set constraint_exclusion to on;

explain (costs off) select * from vt where b is null;
         QUERY PLAN
-----------------------------
 Seq Scan on vt
   Filter: ((a * 2) IS NULL)
(2 rows)

We should get a dummy Result rather than a SeqScan.

What I have in mind is something like the attached v2, which covers
all types of constraints.

- Richard

Attachment

pgsql-hackers by date:

Previous
From: jian he
Date:
Subject: Re: someone else to do the list of acknowledgments
Next
From: Peter Smith
Date:
Subject: Re: Add support for specifying tables in pg_createsubscriber.