Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
Subject: Re: DSO Terms Galore
From: "David E. Wheeler" <david@justatheory.com>
In-Reply-To: <ZprClMExXZGxsAKb@nathan>
Date: Fri, 19 Jul 2024 16:15:28 -0400
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <DBCB8BDB-53AF-4CFE-8DF9-0E019BC2C1E9@justatheory.com>
References: <0B593F46-E673-49BC-A4F7-F27489655284@justatheory.com>
 <ZprClMExXZGxsAKb@nathan>
To: Nathan Bossart <nathandbossart@gmail.com>
Archived-At: <https://www.postgresql.org/message-id/DBCB8BDB-53AF-4CFE-8DF9-0E019BC2C1E9%40justatheory.com>
Precedence: bulk

On Jul 19, 2024, at 15:46, Nathan Bossart <nathandbossart@gmail.com> =
wrote:

> The lack of consistent terminology seems at least potentially =
confusing for
> readers.  My first reaction is that "shared library" is probably fine.

That=E2=80=99s the direction I was leaning, as well, but I thought I =
heard somewhere that the project used the term =E2=80=9Cmodule=E2=80=9D =
for this feature specifically. That would be a bit nicer for the new =
PGXN Meta Spec revision I=E2=80=99m working on[1], where these three =
different types of things could be usefully separated:

* extensions: CREATE EXTENSION extensions
* modules: loadable modules for extensions, hooks, and workers (anything =
else?)
* apps: Programs and scripts like pg_top, pgAdmin, or pg_partman =
scripts[2]

Here the term =E2=80=9Clibraries=E2=80=9D would be a little =
over-generic, and =E2=80=9Cshare_libraries=E2=80=9D longer than I'd like =
(these are JSON object keys).

Best,

David

[1]: https://github.com/pgxn/rfcs/pull/3
[2]: https://github.com/pgpartman/pg_partman/tree/master/bin/common