| From: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
|---|---|
| To: | adminnz(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17759: MERGE UPDATE statements do not cause generated columns to update |
| Date: | 2023-01-25 16:41:10 |
| Message-ID: | CAEZATCXkfNb3cJS5nxTb1+r+5XHWO57buOoq3dL1ngMsFwZHBg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, 25 Jan 2023 at 13:55, PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
>
> A table with "GENERATED ALWAYS" columns do not appear to get updated when
> the update is done via a MERGE statement.
>
Confirmed here, using 15.1. However, it behaves as expected using the
HEAD of the 15 branch.
I think this got fixed as a side-effect of 3706cc97aa [1], though that
commit doesn't explicitly mention MERGE, it does fix a bug in the way
we identified GENERATED columns that need updating, making that
process much more robust.
If so, the fix should be available in 15.2, in a couple of weeks.
(As an aside, perhaps we should add a regression test case for this.)
Thanks for the report.
Regards,
Dean
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pete Storer | 2023-01-25 19:58:37 | Query execution failure |
| Previous Message | David G. Johnston | 2023-01-25 14:12:18 | Re: Minor difference in behavior between +/- |