pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedPossible bug report
2+ messages / 2 participants
[nested] [flat]
* Possible bug report
@ 2022-01-06 22:58 Milos Musicki <mmusicki@yahoo.com>
0 siblings, 1 reply; 2+ messages in thread
From: Milos Musicki @ 2022-01-06 22:58 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
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.
https://stackoverflow.com/questions/70614464/postgresql-insert-into-on-conflict-column-name-is-ambig...
It has to do with INSERT INTO statement when using ON CONFLICT.
All the best.
Milos Musicki
mmusicki@yahoo.com
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Possible bug report
@ 2022-01-07 01:30 David G. Johnston <david.g.johnston@gmail.com>
parent: Milos Musicki <mmusicki@yahoo.com>
0 siblings, 0 replies; 2+ messages in thread
From: David G. Johnston @ 2022-01-07 01:30 UTC (permalink / raw)
To: Milos Musicki <mmusicki@yahoo.com>; +Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
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.
>
> https://stackoverflow.com/questions/70614464/postgresql-
> insert-into-on-conflict-column-name-is-ambiguous
>
> 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.
https://www.postgresql.org/message-id/flat/2A512572-5AE4-4072-9C04-C746C9E67F56%40gmail.com
https://www.postgresql.org/message-id/flat/61A7CB18.20091.3401B246@Jenda.Krynicky.cz
David J.
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2022-01-07 01:30 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-01-06 22:58 Possible bug report Milos Musicki <mmusicki@yahoo.com>
2022-01-07 01:30 ` David G. Johnston <david.g.johnston@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox