Re: ON CONFLICT DO UPDATE using EXCLUDED.column gives an error about mismatched types

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
Cc: Geoff Winkless <pgsqladmin(at)geoff(dot)dj>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ON CONFLICT DO UPDATE using EXCLUDED.column gives an error about mismatched types
Date: 2015-08-04 21:44:52
Message-ID: CAM3SWZQAav_oYKwRcEtgAV6GghF1QC9Ry0qkdUgPxA=M_4J34A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 4, 2015 at 2:29 AM, Amit Langote
<Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> Perhaps, it may have to do with how EXCLUDED pseudo-rel's targetlist is
> manipulated through parse-plan stage?

I think so, yes.

I'll look into writing a fix for this later in the week.

Thanks for the report, Geoff, and thanks for the analysis Amit.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ewan Higgs 2015-08-04 21:55:53 Re: [sqlsmith] Failed assertion in joinrels.c
Previous Message Robert Haas 2015-08-04 21:35:47 Re: max_worker_processes on the standby