Postgres Pro
Downloads
Home   >   mailing lists

Re: Possible bug report - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: Possible bug report
Date
Msg-id CAKFQuwb92=xPM_uKpJ4xCC9WxBRDT_EC=4WxurW=8omLoS=WBA@mail.gmail.com
Whole thread Raw
In response to Possible bug report  (Milos Musicki <mmusicki@yahoo.com>)
List pgsql-bugs
Tree view
On Thursday, January 6, 2022, Milos Musicki <mmusicki@yahoo.com> wrote:
Hello, Miles Musicki here from Michigan, US.
I think I found a bug in PG 13.4, or at least I can't find a reason why it would behave this way.

My question, as well as explanation what I did to avoid the behavior, is displayed here.


It has to do with INSERT INTO statement when using ON CONFLICT.

Thank you for the report - though we prefer that bug reports be self-contained when sent to us.

This unexpected interaction between pl/pgsql and the on conflict clause is known to us (recent thread links below).  There are presently no plans in place to make a behavioral change to this code; users are advised to use one of a number of possible work-arounds to avoid the reported ambiguity error.


David J.

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #17357: When working with the window_function, the Where Clause does not work properly!
Next
From: Etsuro Fujita
Date:
Subject: Re: BUG #17344: Assert failed on queiring async_capable foreign table with inheritance