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

Поиск
Список
Период
Сортировка
От Geoff Winkless
Тема Re: ON CONFLICT DO UPDATE using EXCLUDED.column gives an error about mismatched types
Дата
Msg-id CAEzk6fc4nTwGSnQwbsUu=3AERiGSRRr2bgSveE4J15M-2=WcNA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: ON CONFLICT DO UPDATE using EXCLUDED.column gives an error about mismatched types  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Ответы Re: ON CONFLICT DO UPDATE using EXCLUDED.column gives an error about mismatched types
Список pgsql-hackers
Дерево обсуждения
On 4 August 2015 at 09:30, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp> wrote:
On 2015-08-04 AM 02:57, Peter Geoghegan wrote:
> On Mon, Aug 3, 2015 at 8:53 AM, Geoff Winkless <pgsqladmin@geoff.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​

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: Doubt about AccessExclusiveLock in ALTER TABLE .. SET ( .. );
Следующее
От: Rajeev rastogi
Дата:
Сообщение: Re: Autonomous Transaction is back