| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | hisahiro(at)freemind(dot)co(dot)jp |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17823: Generated columns not always updated correctly |
| Date: | 2023-03-06 16:35:29 |
| Message-ID: | 3402993.1678120529@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> I found that the generated columns are sometimes not updated.
Yeah. Looking into nodeModifyTable.c, we miss re-doing
ExecComputeStoredGenerated when looping back after an EPQ update
(which is what this case is). I see that we also fail to redo that
after a cross-partition move, which is a bug since 8bf6ec3ba.
The attached seems to be enough to fix it, but I want to also devise
an isolation test for these cases ...
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| fix-bug-17823-wip.patch | text/x-diff | 2.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-03-06 21:18:10 | Re: BUG #17823: Generated columns not always updated correctly |
| Previous Message | PG Bug reporting form | 2023-03-06 07:26:42 | BUG #17823: Generated columns not always updated correctly |