Re: [PATCH] Rebuild CHECK constraints after generated column SET EXPRESSION

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] Rebuild CHECK constraints after generated column SET EXPRESSION
Date: 2026-05-28 22:58:13
Message-ID: CAN4CZFMHmb=o_GkJrgEY1iEQpnuDtL_YEHKFZNWG0bdZyozXvA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-05-28 23:19:42 Re: injection_points: Switch wait/wakeup to use atomics rather than latches
Previous Message Chao Li 2026-05-28 22:56:22 Re: Fix bug of CHECK constraint enforceability recursion