Re: PG12 change to DO UPDATE SET column references - Mailing list pgsql-hackers

From Tom Lane
Subject Re: PG12 change to DO UPDATE SET column references
Date
Msg-id 3000510.1705767131@sss.pgh.pa.us
Whole thread Raw
In response to PG12 change to DO UPDATE SET column references  (James Coleman <jtc331@gmail.com>)
Responses Re: PG12 change to DO UPDATE SET column references
List pgsql-hackers
James Coleman <jtc331@gmail.com> writes:
> Suppose I have this table:
> create table foo (id int primary key);

> On PG11 this works:
> postgres=# insert into foo (id) values (1) on conflict (id) do update
> set foo.id = 1;
> INSERT 0 1

Hmm, are you sure about that?  I get

ERROR:  column "foo" of relation "foo" does not exist
LINE 2:   on conflict (id) do update set foo.id = 1;
                                         ^

in every branch back to 9.5 where ON CONFLICT was introduced.

I'm checking branch tip in each case, so conceivably this is
something that was changed post-11.0, but I kinda doubt we
would have back-patched it.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Make documentation builds reproducible
Next
From: Tom Lane
Date:
Subject: Re: Patch: Improve Boolean Predicate JSON Path Docs