From: | Rémi Cura <remi(dot)cura(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | "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:30:08 |
Message-ID: | CAJvUf_v+gJKx3ELH7xvPpkFvdLtMv7oThSVTUgxnFuXW7bVuiQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
thanks for the answer David.
Remi
On Wed, Aug 21, 2024, 15:17 David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> 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.
>
>
> https://www.postgresql.org/message-id/CAKFQuwYZymuC8%3DEtoFRoGM8U79HQArJNWwA8i-JCZRGomkOkdg%40mail.gmail.com
>
> 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 | Tom Lane | 2024-08-21 14:09:58 | Re: CREATE CAST allows creation of binary-coercible cast to range over domain |
Previous Message | David G. Johnston | 2024-08-21 13:17:32 | Re: BUG #18587: PLPGSQL : conflict between variable and ON CONFLICT (a_column) |