> On Dec 21, 2021, at 4:28 PM, Mark Dilger <mark.dil...@enterprisedb.com> wrote:
>
> Maybe there is some reason this is ok.
... and there is. Sorry for the noise. The planner appears to be smart enough
to know that column "salary" is not being changed, and therefore NEW.salary and
OLD.salary are equal. If I test a different update statement that contains a
new value for "salary", the added assertion is not triggered.
(I didn't quite realize what the clause's varnosyn field was telling me until
after I hit "send".)
—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
