Re: [PATCH] Rebuild CHECK constraints after generated column SET EXPRESSION - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [PATCH] Rebuild CHECK constraints after generated column SET EXPRESSION
Date
Msg-id 34e93378-06db-4404-a8e7-3a944912a823@eisentraut.org
Whole thread
In response to Re: [PATCH] Rebuild CHECK constraints after generated column SET EXPRESSION  (jian he <jian.universality@gmail.com>)
Responses Re: [PATCH] Rebuild CHECK constraints after generated column SET EXPRESSION
List pgsql-hackers
On 02.06.26 02:41, jian he wrote:
> On Fri, May 29, 2026 at 6:58 AM Zsolt Parragi <zsolt.parragi@percona.com> wrote:
>>
>> Looks good, I have one nitpick question:
>>
>> +                       if (isnull)
>> +                               elog(WARNING, "null conbin for relation \"%s\"",
>> +                                        RelationGetRelationName(rel));
>>
>> Shouldn't this be an error instead? Most existing checks treat it as
>> an error, and that seems better to me as this shouldn't happen
>> normally?
>>
> OK.
> 
> I changed it to:
>> +                       if (isnull)
>> +                               elog(ERROR, "null conbin for relation \"%s\"",
>> +                                        RelationGetRelationName(rel));
> 
> I also slightly rephrased the commit message.

Committed with some code beautification editorialization.




pgsql-hackers by date:

Previous
From: Jelte Fennema-Nio
Date:
Subject: Re: Can we get rid of TerminateThread() in pg_dump?
Next
From: Peter Eisentraut
Date:
Subject: Re: Fix SET EXPRESSION for virtual columns with whole-row dependencies