| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Thom Brown <thom(at)linux(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, hlinnaka <hlinnaka(at)iki(dot)fi>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 |
| Date: | 2015-05-20 17:37:06 |
| Message-ID: | 20150520173706.GF27868@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
On 2015-05-20 13:31:57 -0400, Tom Lane wrote:
> Sure, but on what basis does it decide that there's a conflict?
>
> If you can't use an exclusion constraint to support the command,
> then the error message shouldn't be worded like that.
But you *can* use a exclusion constraint for DO NOTHING. Just not (yet)
for DO UPDATE.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-05-20 17:55:00 | Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 |
| Previous Message | Tom Lane | 2015-05-20 17:31:57 | Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-05-20 17:37:47 | Re: Typo patch |
| Previous Message | Josh Berkus | 2015-05-20 17:35:26 | Re: Disabling trust/ident authentication configure option |