Re: archive modules

On Wed, Aug 24, 2022 at 10:05:55AM +0200, talk to ben wrote:
>     This view does not display <link linkend="runtime-config-custom">customized options</link>
> -   until the extension module that defines them has been loaded.
> +   until the extension module that defines them has been loaded. Therefore, any
> +   option defined in a library that is dynamically loaded in a separate process
> +   will not be visible in the view, unless the module is manually loaded
> +   beforehand. This case applies for example to an archive module loaded by the
> +   archiver process.

I would suggest something like:

    This view does not display customized options until the extension
    module that defines them has been loaded by the backend process
    executing the query (e.g., via shared_preload_libraries, the LOAD
    command, or a call to a user-defined C function).  For example, since
    the archive_library is only loaded by the archiver process, this view
    will not display any customized options defined by archive modules
    unless special action is taken to load them into the backend process
    executing the query.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com