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

From Pavel Stehule
Subject Re: Bug report for plpgsql
Date
Msg-id CAFj8pRDFnUzSySSWos64TzkvbUBO3Eq79mgXLbsSPy4ps+UHqQ@mail.gmail.com
Whole thread Raw
In response to Re: Bug report for plpgsql  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-bugs
Hi

pá 29. 11. 2024 v 16:41 odesílatel David G. Johnston <david.g.johnston@gmail.com> napsal:
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.


Maybe this issue could be documented. Today is zero documented.

Regards

Pavel


David J.

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Bug report for plpgsql
Next
From: Dave Cramer
Date:
Subject: Re: encrypted pk8 keys work with libpg connection but not in postgres_fdw