Re: DSO Terms Galore

Поиск
Список
Период
Сортировка
Искать
От
David E. Wheeler
Тема
Re: DSO Terms Galore
Дата
Msg-id
DBCB8BDB-53AF-4CFE-8DF9-0E019BC2C1E9@justatheory.com
Ответ на
Re: DSO Terms Galore (Nathan Bossart)
Список
Дерево обсуждения
DSO Terms Galore "David E. Wheeler" <david@justatheory.com>
Re: DSO Terms Galore Peter Eisentraut <peter@eisentraut.org>
Re: DSO Terms Galore "David E. Wheeler" <david@justatheory.com>
Re: DSO Terms Galore Nathan Bossart <nathandbossart@gmail.com>
Re: DSO Terms Galore "David E. Wheeler" <david@justatheory.com>
On Jul 19, 2024, at 15:46, Nathan Bossart  wrote:

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

That’s the direction I was leaning, as well, but I thought I heard somewhere that the project used the term “module” for this feature specifically. That would be a bit nicer for the new PGXN Meta Spec revision I’m 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 “libraries” would be a little over-generic, and “share_libraries” 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



В списке pgsql-hackers по дате отправления
От: David G. Johnston
Дата:
Сообщение: Re: documentation structure
От: Tom Lane
Дата:
Сообщение: Re: documentation structure
FAQ