From: Milos Musicki <mmusicki@yahoo.com>
To: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Possible bug report
Date: Thu, 6 Jan 2022 22:58:31 +0000 (UTC)
Message-ID: <371600056.1505644.1641509911705@mail.yahoo.com> (raw)
References: <371600056.1505644.1641509911705.ref@mail.yahoo.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-bugs@postgresql.org
Cc: mmusicki@yahoo.com
Subject: Re: Possible bug report
In-Reply-To: <371600056.1505644.1641509911705@mail.yahoo.com>
References: <371600056.1505644.1641509911705.ref@mail.yahoo.com> <371600056.1505644.1641509911705@mail.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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