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

Heikki Rauhala <heikki(dot)rauhala(at)reaktor(dot)fi> writes:
> The last insert of the following statements causes a busy loop that does not complete:

> create table gist_test (
> bar text,
> foo text,
> constraint gist_test_bar_unique unique (bar),
> constraint gist_test_foo_gist_unique exclude using gist (foo with =)
> );
> insert into gist_test (bar, foo) values ('bar', 'foo');
> insert into gist_test (bar, foo) values ('baz', 'foo) on conflict on constraint gist_test_bar_unique do nothing;

It looks to me like the ON CONFLICT code has exactly zero chance of
working with non-btree (or more generally, non-amcanunique) indexes.
Was this case ever considered during development?

regards, tom lane