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

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Geoff Winkless <pgsqladmin(at)geoff(dot)dj>
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-08-03 17:57:44
Message-ID: CAM3SWZT58NBPS8npz_2yvqD8JMQzvoUD+gRuQgDKYX91hGK2=w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Aug 3, 2015 at 8:53 AM, Geoff Winkless <pgsqladmin(at)geoff(dot)dj> wrote:
> If I create a copy of the table using
>
> CREATE mytab (LIKE brokentab INCLUDING ALL);
> INSERT INTO mytab SELECT * FROM brokentab;

Also, did you drop any columns from the original "brokentab" table
where the bug can be reproduced?

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2015-08-03 18:35:23 Re: pageinspect patch, for showing tuple data
Previous Message Peter Geoghegan 2015-08-03 17:39:39 Re: ON CONFLICT DO UPDATE using EXCLUDED.column gives an error about mismatched types