| From: | Milos Musicki <mmusicki(at)yahoo(dot)com> |
|---|---|
| To: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Possible bug report |
| Date: | 2022-01-06 22:58:31 |
| Message-ID: | 371600056.1505644.1641509911705@mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
All the best.
Milos Musicki
mmusicki(at)yahoo(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2022-01-07 00:51:40 | BUG #17357: When working with the window_function, the Where Clause does not work properly! |
| Previous Message | Tom Lane | 2022-01-06 20:51:46 | Re: BUG #17351: Altering a composite type created for a partitioned table can lead to a crash |