| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | 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-05 17:31:46 |
| Message-ID: | 20150505173146.GK9855@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
On 2015-04-26 18:02:06 -0700, Peter Geoghegan wrote:
> Remaining challenges
> =================
Another thing I'm wondering about is dealing with deferrable
constraints/deferred indexes.
a) Why does ExecCheckIndexConstraints() check for indisimmediate for
*all* indexes and not just when it's an arbiter index? That seems
needlessly restrictive.
b) There's a doc addition to set_constraints.sgml
+ constraints are affected by this setting. Note that constraints
+ that are <literal>DEFERRED</literal> cannot be used as arbiters by
+ the <literal>ON CONFLICT</> clause that <command>INSERT</>
+ supports.
which I don't think makes sense: SET CONSTRAINTS will never change
anything relevant for ON CONFLICT, right?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Ribe | 2015-05-05 19:03:24 | Re: display to_timestamp in quotas or convert to char ? |
| Previous Message | Andres Freund | 2015-05-05 15:40:30 | Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2015-05-05 17:56:19 | Re: Fixing busted citext function declarations |
| Previous Message | Tom Lane | 2015-05-05 17:20:24 | Re: Fixing busted citext function declarations |