Re: "insert [...] on conflict" hangs on conflict on an unmentioned gist index

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>, Miko Kiiski <miko(dot)kiiski(at)reaktor(dot)com>, Heikki Rauhala <heikki(dot)rauhala(at)reaktor(dot)fi>
Subject: Re: "insert [...] on conflict" hangs on conflict on an unmentioned gist index
Date: 2016-07-04 17:35:46
Message-ID: CAM3SWZSfw0yrpmUBm7KC6gQf4N1nSLnXyodD3zxOOVkVB9bMHg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Jul 4, 2016 at 9:38 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Nah, I take that back --- I was expecting this to be handled somewhere
> else than it is. It looks like the actual cause is just sloppy
> handling of noDupErr in ExecInsertIndexTuples; the attached fixes it
> for me.

I agree that that's all this was; it's uncommon to specify an
exclusion constraint by name with DO NOTHING, so we didn't catch this
until now.

Thanks for looking into this.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Rauhala 2016-07-05 11:44:13 Re: "insert [...] on conflict" hangs on conflict on an unmentioned gist index
Previous Message Tom Lane 2016-07-04 16:38:01 Re: "insert [...] on conflict" hangs on conflict on an unmentioned gist index