| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | hlinnaka <hlinnaka(at)iki(dot)fi> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Subject: | Re: INSERT ... ON CONFLICT error messages |
| Date: | 2015-05-07 18:18:37 |
| Message-ID: | CAM3SWZSXwd3S21dg9VL3iZ50aZbAQ8ebgs4Kmfk-Q_qf=bffZw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 5, 2015 at 8:52 AM, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
> Why not? I would understand if the specified arbiter constraint is deferred,
> but why does it matter if one of the other constraints is?
This has been fixed since, BTW. We now support relations that happen
to have deferred constraints. The constraint indexes cannot be used as
arbiters, but that makes perfect sense.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-05-07 18:24:32 | Re: EvalPlanQual behaves oddly for FDW queries involving system columns |
| Previous Message | Fabien COELHO | 2015-05-07 18:18:16 | PATCH: pgbench allow '=' in \set |