| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "remi(dot)cura(at)gmail(dot)com" <remi(dot)cura(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #18587: PLPGSQL : conflict between variable and ON CONFLICT (a_column) |
| Date: | 2024-08-21 13:17:32 |
| Message-ID: | CAKFQuwb1AxxOBR-0BkUwZypjs8tqdFLSsTa46Xwxkkm+xdQxbg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wednesday, August 21, 2024, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
> The following bug has been logged on the website:
>
> Bug reference: 18587
> Logged by: Rémi Cura
> Email address: remi(dot)cura(at)gmail(dot)com
> PostgreSQL version: 16.3
> Operating system: Linux
> Description:
>
> Writing a PLPGSQL function returning a table with a column named id, and
> using the same column name id in a INSERT ON CONFLICT (id) makes plpgsql
> error.
>
See prior discussions.
In short, the benefit-to-cost ratio to change things here is very low so
it’s likewise a very low priority for everyone who write patches (and
probably needs a fairly experienced hacker too).
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rémi Cura | 2024-08-21 13:30:08 | Re: BUG #18587: PLPGSQL : conflict between variable and ON CONFLICT (a_column) |
| Previous Message | PG Bug reporting form | 2024-08-21 12:34:37 | BUG #18587: PLPGSQL : conflict between variable and ON CONFLICT (a_column) |