From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | remi(dot)cura(at)gmail(dot)com |
Subject: | BUG #18464: Replacing a SQL function silently drops the generated columns that use this function |
Date: | 2024-05-14 15:26:15 |
Message-ID: | 18464-9f1edc4037b65003@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 18464
Logged by: Rémi Cura
Email address: remi(dot)cura(at)gmail(dot)com
PostgreSQL version: 14.10
Operating system: Linux
Description:
I have a SQL function that I defined myself. Let's call it MyFunction().
I use MyFunction in generated columns of 2 distinct tables.
Whe trying to delete MyFunction, the DB correctly raises an error.
However, when I `CREATE OR REPLACE` this existing function in place, the DB
silently drop all the generated columns depending on this function.
This is not the expected behavior.
I should get either an error, or no columns should be dropped.
if they are dropped, I should get at the very least a warning.
This is pretty major: having columns disappear magically on prod dbs is not
what postgres usually do.
From | Date | Subject | |
---|---|---|---|
Next Message | Muhammad Waqas | 2024-05-14 15:42:46 | Re: BUG #18464: Replacing a SQL function silently drops the generated columns that use this function |
Previous Message | Dmitry Dolgov | 2024-05-14 15:18:43 | Re: BUG #18463: Possible bug in stored procedures with polymorphic OUT parameters |