Re: plpgsql: ambiguous column reference in ON CONFLICT clause

2023-02-06 Thread Pavel Stehule
po 6. 2. 2023 v 19:02 odesílatel David G. Johnston < david.g.johns...@gmail.com> napsal: > On Monday, February 6, 2023, Torsten Förtsch > 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

Re: plpgsql: ambiguous column reference in ON CONFLICT clause

2023-02-06 Thread David G. Johnston
On Monday, February 6, 2023, Torsten Förtsch 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 an

Re: plpgsql: ambiguous column reference in ON CONFLICT clause

2023-02-06 Thread Adrian Klaver
On 2/6/23 09:46, Torsten Förtsch wrote: Is there a way to prevent this from happening? I know I can use the PK constraint name or rename the OUT variable i. The question is can this be resolved while keeping the arbiter inference and the variable name. CREATE TABLE x.x (     i INT PRIMARY KEY