Horton

Re: Problem with a "complex" upsert

Mario De Frutos Dieguez <mariodefrutos@gmail.com>

View thread View on postgr.es
From: Mario de Frutos Dieguez <mariodefrutos@gmail.com>
To:
Cc: pgsql-admin@lists.postgresql.org
Date: 2018-06-21T14:46:12Z
Lists: pgsql-bugs 
In this case is just one column but in other queries I'm updating
multiple columns thats why I set the ROW thing

2018-06-21 16:40 GMT+02:00 Geoff Winkless <pgsqladmin@geoff.dj>:
> 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

  1. Fix INSERT ON CONFLICT UPDATE through a view that isn't just SELECT *.