Re: Bug report for plpgsql - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: Bug report for plpgsql
Date
Msg-id CAKFQuwb0jFEVcDDcithXqVgw9ZCHQXrVpB0VypOH=xdoHmsbWQ@mail.gmail.com
Whole thread Raw
In response to Bug report for plpgsql  (Slivaev Dmitry <dmitry.slivaev@gmail.com>)
Responses Re: Bug report for plpgsql
List pgsql-bugs
On Thursday, November 28, 2024, Slivaev Dmitry <dmitry.slivaev@gmail.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.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Build failure with GCC 15 (defaults to -std=gnu23)
Next
From: Pavel Stehule
Date:
Subject: Re: Bug report for plpgsql