Re: Use "protocol options" name instead of "protocol extensions" everywhere - Mailing list pgsql-hackers

From Jelte Fennema-Nio
Subject Re: Use "protocol options" name instead of "protocol extensions" everywhere
Date
Msg-id CAGECzQQ7a+OHrf9KKUPXSNS9tE-C79eV9o+BQPQh4q5aY7qMDg@mail.gmail.com
Whole thread Raw
In response to Re: Use "protocol options" name instead of "protocol extensions" everywhere  (Jelte Fennema-Nio <postgres@jeltef.nl>)
Responses Re: Use "protocol options" name instead of "protocol extensions" everywhere
List pgsql-hackers
On Thu, 31 Oct 2024 at 18:15, Jelte Fennema-Nio <postgres@jeltef.nl> wrote:
>
> On Thu, 31 Oct 2024 at 15:50, Heikki Linnakangas <hlinnaka@iki.fi> wrote:
> > Bikeshedding time:
>
> Another few options:

Okay let's just pick one of the available options. The current
situation where we use different terminology for the same thing across
the docs is definitely confusing, so let's change that. The proposed
options for the names are:

1. Protocol option
2. Protocol extension
3. Optional protocol feature
4. Protocol enhancement
5. Protocol flag
6. Protocol feature-flag
7. Protocol configuration
8. Protocol parameter

My personal preference from most to least preferred are as follows,
but I could live with any of them:

- 1
- 8
- 2
- 7
- everything else

(if we go for "protocol extension" then the patch should be updated to
include a section that clarifies that protocol extensions have nothing
to do with CREATE EXTENSION)



pgsql-hackers by date:

Previous
From: RECHTÉ Marc
Date:
Subject: Re: Logical replication timeout
Next
From: "David G. Johnston"
Date:
Subject: Re: Use "protocol options" name instead of "protocol extensions" everywhere