Re: BUG #16140: View with INSERT, DO INSTEAD, and ON CONFLICT causesan error

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: BUG #16140: View with INSERT, DO INSTEAD, and ON CONFLICT causesan error
Дата
Msg-id CAH2-Wzmfmx_YpAEFGS1rhG_-hdkGfO0yx0hZhxYD0+ww3A5RZA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #16140: View with INSERT, DO INSTEAD, and ON CONFLICT causes an error  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: BUG #16140: View with INSERT, DO INSTEAD, and ON CONFLICT causes an error  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
Дерево обсуждения 
On Thu, Nov 28, 2019 at 10:26 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> You should have written "EXCLUDED.value" not "NEW.value".  There is
> a bug here, but it's that the parser accepted this rule.   I'm guessing
> that the parsing logic for ON CONFLICT didn't consider the possibility
> that NEW and OLD for a rule would already be in the range table.

I must admit that I have zero recollection of this aspect of the ON
CONFLICT work. Do you think that this would be difficult to fix?

-- 
Peter Geoghegan

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

Предыдущее
От: Justin Pryzby
Дата:
Сообщение: Re: BUG #16111: Unexpected query compilation error “negative bitmapset member not allowed”
Следующее
От: "David G. Johnston"
Дата:
Сообщение: Re: BUG #16149: Prepared COPY queries always report 0 parameters when described