Re: BUG #18464: Replacing a SQL function silently drops the generated columns that use this function

Awesome!
The irony is that I triggered this behavior while solving issues in order
to upgrade to PG16 :-)
thank you very much again
Rémi

On Wed, May 15, 2024, 17:56 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> =?UTF-8?Q?R=C3=A9mi_Cura?= <remi(dot)cura(at)gmail(dot)com> writes:
> > I tried to reproduce, and as you pointed out, updating the function in
> > place is not what dropped the columns.
> > Instead, I must have dropped and recreated the function, which indeed
> drops
> > the generated columns.
> > I still feel this is a very dangerous behavior.
>
> Yeah, we changed this at v15. See
>
>
> https://www.postgresql.org/message-id/flat/17439-7df4421197e928f0%40postgresql.org
>
>
> https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=cb02fcb4c
>
> regards, tom lane
>