| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Slivaev Dmitry <dmitry(dot)slivaev(at)gmail(dot)com> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Bug report for plpgsql |
| Date: | 2024-11-29 15:41:11 |
| Message-ID: | CAKFQuwb0jFEVcDDcithXqVgw9ZCHQXrVpB0VypOH=xdoHmsbWQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thursday, November 28, 2024, Slivaev Dmitry <dmitry(dot)slivaev(at)gmail(dot)com>
wrote:
> Postrgesql version
>
> PostgreSQL 17.0 (Debian 17.0-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
>
>
> *Description:*
> When a RETURNS TABLE function in PL/pgSQL includes a column name that
> matches a column in a table being targeted for an ON CONFLICT clause,
> PostgreSQL throws an error stating that the column reference is ambiguous.
> This happens even though the context of ON CONFLICT unambiguously refers
> to table column names, not PL/pgSQL variables.
> This behavior leads to unexpected errors in scenarios where the function's RETURNS
> TABLE includes columns with the same name as those in the target table.
> Explicit qualification of column names in ON CONFLICT (e.g., table.column)
> also fails to resolve the issue.
>
Yes, this is a known limitation that has a very low priority for being
fixed. You can find more discussion on the mailing list archives.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2024-11-29 15:48:56 | Re: Bug report for plpgsql |
| Previous Message | Tom Lane | 2024-11-29 15:31:53 | Re: Build failure with GCC 15 (defaults to -std=gnu23) |