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 CAGECzQSydaBQoYCQSJ5BQJKP+Zv2wHLSU2CcmpxJ4UV0DWPwLg@mail.gmail.com
Whole thread Raw
In response to Re: Use "protocol options" name instead of "protocol extensions" everywhere  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Thu, 31 Oct 2024 at 17:09, Robert Haas <robertmhaas@gmail.com> wrote:
> I don't think it's really viable to promise that we'll never talk
> about extending anything other than in the context of what CREATE
> EXTENSION does.

Agreed, but it seems nice to avoid confusion by not overloading
terminology, if we can find a good/decent alternative. When we do have
an overloaded term, we should definitely document what we mean with it
and how it differs from other usage of the term. But even then many
people won't have read those docs and assume it means the thing that
they expect it to mean.

A good example of this is the fact that initdb creates a "database
cluster". We definitely document that we use the term that way. But if
you talk/write about a database cluster many people (understandably)
expect you to mean a very different thing.



pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: "command cannot affect row a second time" in INSERT ... ON CONFLICT
Next
From: "Andrey M. Borodin"
Date:
Subject: Re: MultiXact\SLRU buffers configuration