| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Torsten Förtsch <tfoertsch123(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: plpgsql: ambiguous column reference in ON CONFLICT clause |
| Date: | 2023-02-06 18:02:21 |
| Message-ID: | CAKFQuwYZymuC8=EtoFRoGM8U79HQArJNWwA8i-JCZRGomkOkdg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Monday, February 6, 2023, Torsten Förtsch <tfoertsch123(at)gmail(dot)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.
https://www.postgresql.org/message-id/1990141.1638388378%40sss.pgh.pa.us
https://www.postgresql.org/message-id/flat/15533-ac9506ee433a0d18%40postgresql.org
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sebastien Flaesch | 2023-02-06 18:03:53 | Re: Get the sequence name corresponding to a GENERATED { ALWAYS | BY DEFAULT } AS IDENTITY column |
| Previous Message | Adrian Klaver | 2023-02-06 17:50:12 | Re: plpgsql: ambiguous column reference in ON CONFLICT clause |