Re: bug in stored generated column over domain with constraints.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: jian he <jian(dot)universality(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: bug in stored generated column over domain with constraints.
Date: 2025-04-15 16:13:49
Message-ID: 1697097.1744733629@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

jian he <jian(dot)universality(at)gmail(dot)com> writes:
> Thanks for simplifying the tests, overall all looks good.

OK, pushed and back-patched, but only to v14. I tried to make
a variant that'd work in v13, but it caused ExecCheckPlanOutput
to throw "Query provides a value for a generated column" errors
for UPDATEs. That's surely related to the major refactoring of
UPDATE targetlists that we did in v14. Given that we've had
zero field complaints about this problem so far, I think the
risk of breaking something in v13 exceeds the value of fixing
the bug, so I left v13 alone.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nico Williams 2025-04-15 16:16:46 Re: Wrong security context for deferred triggers?
Previous Message Dimitrios Apostolou 2025-04-15 16:02:40 Re: Fundamental scheduling bug in parallel restore of partitioned tables