| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "ketan(dot)bhatiya(at)lenditt(dot)com" <ketan(dot)bhatiya(at)lenditt(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <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:46:03 |
| Message-ID: | CAKFQuwYX2UNBngm2Qce+aA=4kc-OBsccNaRvvBoQ2disCyXFMg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Friday, September 26, 2025, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
> The following bug has been logged on the website:
>
> Bug reference: 19064
> Logged by: Ketan Bhatiya
> Email address: ketan(dot)bhatiya(at)lenditt(dot)com
> PostgreSQL version: Unsupported/Unknown
> Operating system: Windows
> Description:
>
> 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.
>
>
The bug reporting list should not be used for feature requests. Those
should be directed to -general.
It seems unlikely anyone is going to spend time on this though. You are
expected to test what you write and this fails immediately and obviously.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rahila Syed | 2025-09-26 12:59:45 | Re: BUG #19064: Trigger allows creation with invalid column references but fails at runtime |
| Previous Message | Todd Cook | 2025-09-26 12:30:36 | Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 |