Re: Problem with a "complex" upsert
Geoff Winkless <pgsqladmin@geoff.dj>
From: Geoff Winkless <pgsqladmin@geoff.dj>
To: mariodefrutos@gmail.com
Cc: pgsql-admin@lists.postgresql.org
Date: 2018-06-21T14:40:51Z
Lists: pgsql-bugs
On Thu, 21 Jun 2018 at 15:07, Mario De Frutos Dieguez < mariodefrutos@gmail.com> wrote: > ON CONFLICT (geoid) DO UPDATE SET (b01003001) = ROW(EXCLUDED.b01003001); > At first glance, shouldn't the query simply be SET b01003001 = EXCLUDED.b01003001; ? The second part of your email does suggest a bug though, syntax shouldn't cause a crash. Geoff
Commits
-
Fix INSERT ON CONFLICT UPDATE through a view that isn't just SELECT *.
- 5ad143cda092 9.5.14 landed
- f6a124d019a4 10.5 landed
- e7154b6acfeb 11.0 landed
- b8a1247a34e2 12.0 landed
- b484bffe7d0e 9.6.10 landed