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

From: Geoff Winkless <pgsqladmin(at)geoff(dot)dj>
To: 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 08:58:23
Message-ID: CAEzk6fc4nTwGSnQwbsUu=3AERiGSRRr2bgSveE4J15M-2=WcNA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 4 August 2015 at 09:30, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
wrote:

> On 2015-08-04 AM 02:57, Peter Geoghegan wrote:
> > 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?
> >
>
> This seem to be the case. I could reproduce the reported problem:
>

​Although it seems Amit has defined the problem better than I could, so
this is a bit late to the party (!), yes, the table had been ALTERed after
it was created (looking back through the history, that modification
included at least one DROP COLUMN).

Thanks

Geoff​

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Rajeev rastogi 2015-08-04 09:12:24 Re: Autonomous Transaction is back
Previous Message Andres Freund 2015-08-04 08:55:03 Re: Doubt about AccessExclusiveLock in ALTER TABLE .. SET ( .. );