Re: A Typo in regress/sql/privileges.sql - Mailing list pgsql-hackers

From Robert Haas
Subject Re: A Typo in regress/sql/privileges.sql
Date
Msg-id CA+TgmoYFe88itO31YnzzepR7C_+Go9VeHp2jeiD7eyR0Np=0XQ@mail.gmail.com
Whole thread Raw
In response to Re: A Typo in regress/sql/privileges.sql  (Peter Geoghegan <pg@heroku.com>)
Responses Re: A Typo in regress/sql/privileges.sql  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
On Tue, Dec 22, 2015 at 2:23 PM, Peter Geoghegan <pg@heroku.com> wrote:
> On Tue, Dec 22, 2015 at 11:01 AM, Robert Haas <robertmhaas@gmail.com> wrote:
>>> TBH I'm kinda inclined to sort this out by removing all usage of the
>>> word "inference" everywhere --- error messages and code comments and
>>> documentation wording, and replace it with some other wording as
>>> appropriate for each context.
>>
>> I would not object to that.
>
> Why? There is nothing wrong with the term inference. It's perfectly
> descriptive. It's also a term I've used as part of many talks about ON
> CONFLICT. No one has said a word about it before now.

If it's an axiom that there is nothing wrong with the term inference,
then obviously we should not change anything.  But that seems to me to
be putting the cart before the horse.

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Using quicksort for every external sort run
Next
From: Robert Haas
Date:
Subject: Re: Re: Reusing abbreviated keys during second pass of ordered [set] aggregates