Re: Bug report for plpgsql
От | David G. Johnston |
---|---|
Тема | Re: Bug report for plpgsql |
Дата | |
Msg-id | CAKFQuwb0jFEVcDDcithXqVgw9ZCHQXrVpB0VypOH=xdoHmsbWQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Bug report for plpgsql (Slivaev Dmitry <dmitry.slivaev@gmail.com>) |
Ответы |
Re: Bug report for plpgsql
|
Список | pgsql-bugs |
On Thursday, November 28, 2024, Slivaev Dmitry <dmitry.slivaev@gmail.com> wrote:
Postrgesql versionPostgreSQL 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 aRETURNS TABLE
function in PL/pgSQL includes a column name that matches a column in a table being targeted for anON CONFLICT
clause, PostgreSQL throws an error stating that the column reference is ambiguous. This happens even though the context ofON CONFLICT
unambiguously refers to table column names, not PL/pgSQL variables.
This behavior leads to unexpected errors in scenarios where the function'sRETURNS TABLE
includes columns with the same name as those in the target table. Explicit qualification of column names inON 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 по дате отправления: