Re: COPY FROM ON_ERROR SET_NULL bypasses domain NOT NULL with partial column list - Mailing list pgsql-hackers

From jian he
Subject Re: COPY FROM ON_ERROR SET_NULL bypasses domain NOT NULL with partial column list
Date
Msg-id CACJufxEYGY5twGooBDU4ttpb0SOQuOb8dYKoBsEML8dObAf4ZQ@mail.gmail.com
Whole thread
In response to COPY FROM ON_ERROR SET_NULL bypasses domain NOT NULL with partial column list  (SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>)
List pgsql-hackers
On Fri, Apr 17, 2026 at 1:09 AM SATYANARAYANA NARLAPURAM
<satyanarlapuram@gmail.com> wrote:
>
> HI hackers,
>
> domain_with_constraint[] was allocated with list_length(attnumlist)
> elements and indexed sequentially via foreach_current_index(), but
> copyfromparse.c accesses it via attnum - 1 (physical attribute index).
> With a partial column list targeting high-numbered columns, this caused
> an out-of-bounds read that bypassed domain NOT NULL checks, silently
> inserting NULL into NOT NULL domain columns.
>
> Fix by allocating with num_phys_attrs and indexing by attnum - 1,
> consistent with all other per-column arrays in BeginCopyFrom().
>
> Patch is attached, and added a new test case to cover this scenario.
>

The patch looks good to me.
I simplified the tests.



--
jian
https://www.enterprisedb.com/

Attachment

pgsql-hackers by date:

Previous
From: Xiaopeng Wang
Date:
Subject: Re: [doc] pg_ctl: fix wrong description for -l
Next
From: Lakshmi N
Date:
Subject: Re: Reject invalid databases in pg_get_database_ddl()