Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #16140: View with INSERT, DO INSTEAD, and ON CONFLICT causesan error - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: BUG #16140: View with INSERT, DO INSTEAD, and ON CONFLICT causesan error
Date
Msg-id CAH2-Wzmfmx_YpAEFGS1rhG_-hdkGfO0yx0hZhxYD0+ww3A5RZA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #16140: View with INSERT, DO INSTEAD, and ON CONFLICT causes an error  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #16140: View with INSERT, DO INSTEAD, and ON CONFLICT causes an error  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tree view 
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 by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: BUG #16111: Unexpected query compilation error “negative bitmapset member not allowed”
Next
From: "David G. Johnston"
Date:
Subject: Re: BUG #16149: Prepared COPY queries always report 0 parameters when described