| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Amul Sul <sulamul(at)gmail(dot)com>, Vaibhav Dalvi <vaibhav(dot)dalvi(at)enterprisedb(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: ALTER COLUMN ... SET EXPRESSION to alter stored generated column's expression |
| Date: | 2023-10-06 12:33:40 |
| Message-ID: | 91fda353-8974-5c2f-54b3-4a0af42d93eb@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 28.08.23 11:54, Amul Sul wrote:
> Thanks for the review comments, I have fixed those in the attached
> version. In
> addition to that, extended syntax to have the STORE keyword as suggested by
> Vik.
An additional comment: When you change the generation expression, you
need to run ON UPDATE triggers on all rows, if there are any triggers
defined. That is because someone could have triggers defined on the
column to either check for valid values or propagate values somewhere
else, and if the expression changes, that is kind of like an UPDATE.
Similarly, I think we should consider how logical decoding should handle
this operation. I'd imagine it should generate UPDATE events on all
rows. A test case in test_decoding would be useful.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2023-10-06 12:36:10 | Re: Two Window aggregate node for logically same over clause |
| Previous Message | Ashutosh Bapat | 2023-10-06 12:16:19 | Re: FDW pushdown of non-collated functions |