From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | James Coleman <jtc331(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PG12 change to DO UPDATE SET column references |
Date: | 2024-01-19 18:53:03 |
Message-ID: | CAKFQuwYLNDzj1+kvig03hLiaj6SmWu-Fxc5oU+cQBL+-+7tsiw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jan 19, 2024 at 10:01 AM James Coleman <jtc331(at)gmail(dot)com> wrote:
> Making this more confusing is the fact that if I want to do something
> like "SET bar = foo.bar + 1" the table qualification cannot be present
> on the setting column but is required on the reading column.
>
> There isn't anything in the docs that I see about this, and I don't
> see anything scanning the release notes for PG12 either (though I
> could have missed a keyword to search for).
>
>
https://www.postgresql.org/docs/12/sql-insert.html
"When referencing a column with ON CONFLICT DO UPDATE, do not include the
table's name in the specification of a target column. For example, INSERT
INTO table_name ... ON CONFLICT DO UPDATE SET table_name.col = 1 is invalid
(this follows the general behavior for UPDATE)."
The same text exists for v11.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-01-19 19:32:27 | Improving EXPLAIN's display of SubPlan nodes |
Previous Message | David Christensen | 2024-01-19 18:49:03 | Re: [PATCHES] Post-special page storage TDE support |