Re: [PATCH][Documination] Add optional USING keyword before opclass name in INSERT statemet - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [PATCH][Documination] Add optional USING keyword before opclass name in INSERT statemet
Date
Msg-id CA+TgmobTbtbdTqVQMv9XQctO26ENv8ur9vjqg3xDsLfBdNrEQQ@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH][Documination] Add optional USING keyword before opclass name in INSERT statemet  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCH][Documination] Add optional USING keyword before opclass name in INSERT statemet
List pgsql-hackers
On Tue, May 31, 2016 at 12:34 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> On Thu, May 26, 2016 at 3:28 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> 99% of the time, you'd be right.  But this is an unusual case, for the
>>> reasons I mentioned before.
>
>> I tend to agree with Nikolay.  I can't see much upside in making this
>> change.  At best, nothing will break.  At worst, something will break.
>> But how do we actually come out ahead?
>
> We come out ahead by not having to make the documentation more confusing.
>
> Basically, we have the opportunity to fix an ancient mistake here at
> very low cost.  I do not think that doubling down on the mistake is
> a better answer.

I'm not convinced, but we don't have to agree on everything...

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Rename max_parallel_degree?
Next
From: "David G. Johnston"
Date:
Subject: Re: Rename max_parallel_degree?