| From: | Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: ON CONFLICT with constraint name doesn't work |
| Date: | 2017-04-26 16:14:17 |
| Message-ID: | CANNMO+K_tWMzE_YjyFxDDQq2+oJ1iUShB2_KVm2jLo4A6=7TiA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
This is a kindly reminder, that this problem (message about "constraint"
violation, while there is no such a constraint defined, just an index) is
still unresolved.
Let's fix that naming?
Patch is attached in the previous message (posted to -bugs list)
On Thu, Mar 16, 2017 at 9:15 PM, Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com>
wrote:
>
> Anyway, attached are 2 separate patches:
> 1) version 2 of patch fixing the message, including regression tests;
> 2) proposed change to the documentation https://www.postgresql.org/
> docs/current/static/sql-insert.html
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-04-26 16:15:53 | Re: Concurrent ALTER SEQUENCE RESTART Regression |
| Previous Message | Michael Paquier | 2017-04-26 01:24:40 | Re: Concurrent ALTER SEQUENCE RESTART Regression |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-04-26 16:15:03 | Re: Dropping a partitioned table takes too long |
| Previous Message | Peter Eisentraut | 2017-04-26 16:10:40 | Re: logical replication fixes |