Re: [HACKERS] INSERT .. ON CONFLICT DO SELECT [FOR ..] - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [HACKERS] INSERT .. ON CONFLICT DO SELECT [FOR ..]
Date
Msg-id CAB7nPqRAbN-V9wDWAXe10GpmJAVW7KW9vQeGkPrOPHPr7jKVzw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] INSERT .. ON CONFLICT DO SELECT [FOR ..]  (Marko Tiikkaja <marko@joh.to>)
Responses Re: [HACKERS] INSERT .. ON CONFLICT DO SELECT [FOR ..]  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-hackers
On Tue, Sep 5, 2017 at 3:28 AM, Marko Tiikkaja <marko@joh.to> wrote:
> On Mon, Sep 4, 2017 at 7:46 PM, Peter Geoghegan <pg@bowt.ie> wrote:
>>
>> On Mon, Sep 4, 2017 at 10:05 AM, Marko Tiikkaja <marko@joh.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.

The patch does not currently apply. I am noticing as well that Peter
Geoghegan has registered himself as a reviewer a couple of hours back,
so moved to next CF with waiting on author as status.
-- 
Michael


pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] GSOC'17 project introduction: Parallel COPY executionwith errors handling
Next
From: Tom Lane
Date:
Subject: Re: pl/perl extension fails on Windows