| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Amul Sul <sulamul(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Vaibhav Dalvi <vaibhav(dot)dalvi(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: ALTER COLUMN ... SET EXPRESSION to alter stored generated column's expression |
| Date: | 2023-11-07 14:51:20 |
| Message-ID: | 30e56b77-3685-48ea-8954-9b8845f84e04@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 25.10.23 08:12, Amul Sul wrote:
> Here is the rebase version for the latest master head(673a17e3120).
>
> I haven't done any other changes related to the ON UPDATE trigger since that
> seems non-trivial; need a bit of work to add trigger support in
> ATRewriteTable().
> Also, I am not sure yet, if we were doing these changes, and the correct
> direction
> for that.
I did some detailed testing on Db2, Oracle, and MariaDB (the three
existing implementations of this feature that I'm tracking), and none of
them fire any row or statement triggers when the respective statement to
alter the generation expression is run. So I'm withdrawing my comment
that this should fire triggers. (I suppose event triggers are available
if anyone really needs the functionality.)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-11-07 14:53:35 | Re: GUC names in messages |
| Previous Message | Dean Rasheed | 2023-11-07 14:33:55 | Re: Infinite Interval |