| From: | Geoff Winkless <pgsqladmin(at)geoff(dot)dj> |
|---|---|
| To: | mariodefrutos(at)gmail(dot)com |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Problem with a "complex" upsert |
| Date: | 2018-06-21 14:40:51 |
| Message-ID: | CAEzk6ff6xJyujo88jUa4n2CtqYMJnKtJPXB9=9H2gSZxj+SdDA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-bugs |
On Thu, 21 Jun 2018 at 15:07, Mario De Frutos Dieguez <
mariodefrutos(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mario de Frutos Dieguez | 2018-06-21 14:46:12 | Re: Problem with a "complex" upsert |
| Previous Message | Mario De Frutos Dieguez | 2018-06-21 14:11:09 | Fwd: Problem with a "complex" upsert |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mario de Frutos Dieguez | 2018-06-21 14:46:12 | Re: Problem with a "complex" upsert |
| Previous Message | Mario De Frutos Dieguez | 2018-06-21 14:11:09 | Fwd: Problem with a "complex" upsert |