Postgres Pro
Downloads
Home   >   mailing lists

Re: plpgsql: ambiguous column reference in ON CONFLICT clause - Mailing list pgsql-general

From David G. Johnston
Subject Re: plpgsql: ambiguous column reference in ON CONFLICT clause
Date
Msg-id CAKFQuwYZymuC8=EtoFRoGM8U79HQArJNWwA8i-JCZRGomkOkdg@mail.gmail.com
Whole thread Raw
In response to plpgsql: ambiguous column reference in ON CONFLICT clause  (Torsten Förtsch <tfoertsch123@gmail.com>)
Responses Re: plpgsql: ambiguous column reference in ON CONFLICT clause  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-general
Tree view
On Monday, February 6, 2023, Torsten Förtsch <tfoertsch123@gmail.com> wrote:

After reading this I am wondering if the current behavior is actually a bug.

Arguably it is a bug, and a known one at that if you want some light reading, but regardless there is presently no proposal to get rid of the POLA violation and little chance for any solution to be back-patched since the issue is lack of good existing technical options.



David J.

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: plpgsql: ambiguous column reference in ON CONFLICT clause
Next
From: Sebastien Flaesch
Date:
Subject: Re: Get the sequence name corresponding to a GENERATED { ALWAYS | BY DEFAULT } AS IDENTITY column