Re: BUG #18587: PLPGSQL : conflict between variable and ON CONFLICT (a_column) - Mailing list pgsql-bugs

From Rémi Cura
Subject Re: BUG #18587: PLPGSQL : conflict between variable and ON CONFLICT (a_column)
Date
Msg-id CAJvUf_v+gJKx3ELH7xvPpkFvdLtMv7oThSVTUgxnFuXW7bVuiQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18587: PLPGSQL : conflict between variable and ON CONFLICT (a_column)  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-bugs

thanks for the answer David.
Remi

On Wed, Aug 21, 2024, 15:17 David G. Johnston <david.g.johnston@gmail.com> wrote:
On Wednesday, August 21, 2024, PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      18587
Logged by:          Rémi Cura
Email address:      remi.cura@gmail.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.

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #18587: PLPGSQL : conflict between variable and ON CONFLICT (a_column)
Next
From: Tom Lane
Date:
Subject: Re: CREATE CAST allows creation of binary-coercible cast to range over domain