From: | Rahila Syed <rahilasyed90(at)gmail(dot)com> |
---|---|
To: | ketan(dot)bhatiya(at)lenditt(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #19064: Trigger allows creation with invalid column references but fails at runtime |
Date: | 2025-09-26 12:59:45 |
Message-ID: | CAH2L28uPfAbipMeAa+XTfGck4Nwo7yv8o+FwZor7f7ivDOS8vg@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi
> Suggestion / Proposed Improvement
> PostgreSQL should validate column references at trigger creation time, not
> just at runtime.
> If a column does not exist in the target table (Orders in this example),
> trigger creation should fail immediately with a clear error message.
>
>
This behaviour is by design in PostgreSQL. The CreateTrigger() is
responsible
for creating a dependency between trigger and its underlying pl/pgsql
function.
The pl/pgsql function is only parsed when it is executed for the first time.
This approach allows for flexibility, such as adding columns to a table
after a trigger
has been created. On the other hand, if a column existing at the time of
trigger creation
is later removed, validating at creation time would not offer much
advantage in these
situations.
Thank you,
Rahila Syed
From | Date | Subject | |
---|---|---|---|
Next Message | Álvaro Herrera | 2025-09-26 13:34:38 | Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c |
Previous Message | David G. Johnston | 2025-09-26 12:46:03 | Re: BUG #19064: Trigger allows creation with invalid column references but fails at runtime |