Re: INSERT .. ON CONFLICT DO SELECT [FOR ..]

From: Marko Tiikkaja <marko(at)joh(dot)to>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: INSERT .. ON CONFLICT DO SELECT [FOR ..]
Date: 2017-09-04 18:28:57
Message-ID: CAL9smLAu8X7DLWdJ7NB0BtcN=_kCz33Fz6WYUBDRysWdG0yFig@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Sep 4, 2017 at 7:46 PM, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:

> On Mon, Sep 4, 2017 at 10:05 AM, Marko Tiikkaja <marko(at)joh(dot)to> wrote:

> But I'm generally against
> > interfaces which put arbitrary restrictions on what power users can do on
> > the basis that less experienced people might misuse the interface.
>
> I agree with that as a broad principle, but disagree that it applies
> here. Or if it does, then you have yet to convince me of it. In all
> sincerity, if you think that I just don't understand your perspective,
> then please try to make me understand it. Would a power user actually
> miss ON CONFLICT DO SELECT? And if that's the case, would it really be
> something they'd remember 5 minutes later?
>

I don't know, but I don't want to be limiting what people can do just
because I can't come up with a use case.

In any case, others, feel free to chime in.

.m

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2017-09-04 19:12:40 Re: pgbench - allow to store select results into variables
Previous Message Emre Hasegeli 2017-09-04 18:07:23 Re: [PATCH] Improve geometric types