Re: Use "protocol options" name instead of "protocol extensions" everywhere

From: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Use "protocol options" name instead of "protocol extensions" everywhere
Date: 2024-10-31 17:25:33
Message-ID: CAGECzQSydaBQoYCQSJ5BQJKP+Zv2wHLSU2CcmpxJ4UV0DWPwLg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 31 Oct 2024 at 17:09, Robert Haas <robertmhaas(at)gmail(dot)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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey M. Borodin 2024-10-31 17:32:42 Re: MultiXact\SLRU buffers configuration
Previous Message Bruce Momjian 2024-10-31 17:22:51 Re: DOCS - pg_replication_slot . Fix the 'inactive_since' description