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

From: Andres Freund <andres(at)anarazel(dot)de>
To: Geoff Winkless <pgsqladmin(at)geoff(dot)dj>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Peter Geoghegan <pg(at)heroku(dot)com>
Cc: 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-10-03 13:18:56
Message-ID: 20151003131856.GC5801@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

> db=# INSERT INTO brokentab(id, k1,k2,k3,k4,k5,k6,k7, smallval) VALUES
> (5,0,0,0,1,0,1,0, 0) ON CONFLICT (id, k1,k2,k3,k4,k5,k6,k7) DO UPDATE SET
> smallval=EXCLUDED.smallval;
> ERROR: attribute 29 has wrong type
> DETAIL: Table has type integer, but query expects smallint.

I pushed a fix for the issue. Could you verify that your original
problem does not exist anymore?

Thanks for testing Geoff, thanks for helping to nail this down Amit and
Peter.

Regards,

Andres

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2015-10-03 13:31:07 Re: Why can't we used CAPITAL LETTERS into replication slot_name?
Previous Message Amir Rohan 2015-10-03 13:04:45 Re: In-core regression tests for replication, cascading, archiving, PITR, etc.