| 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> |
| Subject: | Re: ON CONFLICT with constraint name doesn't work |
| Date: | 2017-03-16 20:56:27 |
| Message-ID: | CANNMO+Kzj=VVUYeDDz-UtvOcVnkhrQ6CvWRAD=G0j8d943cVHA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Thu, Mar 16, 2017 at 1:23 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>
> Seems like a good idea to improve that message. I wouldn't vote for
> backpatching it, however. Could you propose a patch for that?
>
OK. Here it is.
But:
1) what's next with all the i18n stuff? I've changed RU version as well,
but unfortunately I don't the other languages.
2) it will definitely break many regression tests, should I patch them as
well?
Also, documentation explaining ON CONFLICT might be still not clear, at
least for some readers. Do you want me to propose a patch for that as well?
| Attachment | Content-Type | Size |
|---|---|---|
| fix_messaging_unique_index_vs_constraint.patch | application/octet-stream | 1.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-03-16 20:59:18 | Re: ON CONFLICT with constraint name doesn't work |
| Previous Message | Andres Freund | 2017-03-16 20:37:50 | Re: BUG #14057: vacuum setting reltuples=0 for tables with >0 tuples |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Corey Huinker | 2017-03-16 20:57:50 | Re: \if, \elseif, \else, \endif (was Re: PSQL commands: \quit_if, \quit_unless) |
| Previous Message | Stephen Frost | 2017-03-16 20:41:48 | Re: GSOC - TOAST'ing in slices |