Re: ON CONFLICT with constraint name doesn't work

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: ON CONFLICT with constraint name doesn't work
Date: 2017-03-16 19:51:18
Message-ID: CAH2-Wz=o5eMFH20Yw2h9hrn0TxkGZpM0zq1Uw9xoWjMPP9CDEg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Thu, Mar 16, 2017 at 12:49 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> FWIW, I never was completely on board with this design goal, and I think
> we should have (and still should) support using indexes directly.

FWIW I agree that we probably should have exposed indexes as a target
that can be named directly, while still generally discouraging the
practice. But, it hardly matters now.

--
Peter Geoghegan

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Nikolay Samokhvalov 2017-03-16 20:08:53 Re: ON CONFLICT with constraint name doesn't work
Previous Message Andres Freund 2017-03-16 19:49:08 Re: ON CONFLICT with constraint name doesn't work

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-03-16 20:07:34 Re: Parallel Append implementation
Previous Message Andres Freund 2017-03-16 19:49:08 Re: ON CONFLICT with constraint name doesn't work