Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oRJ7C-0001lH-SQ for pgsql-hackers@arkaria.postgresql.org; Thu, 25 Aug 2022 20:06:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oRJ7B-0002D5-NJ for pgsql-hackers@arkaria.postgresql.org; Thu, 25 Aug 2022 20:06:09 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oRJ7B-0002Cp-CX for pgsql-hackers@lists.postgresql.org; Thu, 25 Aug 2022 20:06:09 +0000 Received: from mail-pj1-x1035.google.com ([2607:f8b0:4864:20::1035]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oRJ76-0006h7-JR for pgsql-hackers@postgresql.org; Thu, 25 Aug 2022 20:06:08 +0000 Received: by mail-pj1-x1035.google.com with SMTP id hf17so2723404pjb.3 for ; Thu, 25 Aug 2022 13:06:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc; bh=LaV1s5zXOkemVlxGc792VhrmS1Uy9oPxeh+YOiP+Ypw=; b=WIDoDj8N2JZSOmdIKC+cE6zdCk/mnXBkynTyjFYg1fkJcQJJSmLe221NR48owzwJW0 BB7w5rNXsrQFauoWWpoIDC9wtukLjPRmYNhD/Kkziip86Pu2dDt1xkvvbXAZm69/1oh3 nZbcP3PMZymDbQbFU+AO30OCIK1BcUdna69Mw1GyhMTdeyQ0vGIfVdqKe2QrVm2nGOug drJuTWyW3Blk5KJY9VcO/qndHNko5l+x89I4cEDgWRdGp7lz43EiLM4BzTUhHTEHJEH4 UQ5gqjpcRP7g1UTntvzZacf8+YXaHYxnKeeqwqpOXtBaZnNIi9mB+fAx88FFZsZ4wPv3 qrnA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc; bh=LaV1s5zXOkemVlxGc792VhrmS1Uy9oPxeh+YOiP+Ypw=; b=5T7NME7GWGerjlXteO0Slxb7T4Wn8Plf+jygbsHy6CxJnT562skCB1IVvoFByOD4oR 1OF6r5YOzI3LDa+ano2xTbgUzuh5vEkmhrFoKQDadbfcy4rChUmLI+A8cOA8O+hijhLI gm8MlUn5f59pslGKIVtxNsexem9q9G0pUcW8nDGG8gFCYDPBtR7Su5PpXt9pYN+gTtPp w8eJREjtduZEuw69s5EuiPenNLfamiSNhJDMA+kGIgXvEIQsFgsqidNq2MsJw6ClbNIt tbup4QkBbst15AUz0e5iyQkIDXFRWK4OrVZurnwtbrRDbpL0Ey1/ztgEVpRFPcfaD4DK ZyNg== X-Gm-Message-State: ACgBeo3PF+09zl44No7EL5cyjPteNHy069QBGRl/94AdpveSSuXBqfMB YXSLSvZoRgoseJ6Baz2p8zY= X-Google-Smtp-Source: AA6agR7r+korH2JKzc+0e9HAhw7pc0jYTU3T6/unFrkZcLoCRCppi+/jnj7NdXpmgwKHqPdYClOORg== X-Received: by 2002:a17:902:f782:b0:173:1206:cee0 with SMTP id q2-20020a170902f78200b001731206cee0mr663150pln.130.1661457963565; Thu, 25 Aug 2022 13:06:03 -0700 (PDT) Received: from nathanxps13 ([50.47.162.83]) by smtp.gmail.com with ESMTPSA id i36-20020a17090a3da700b001fba4716f11sm119523pjc.22.2022.08.25.13.06.01 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 25 Aug 2022 13:06:02 -0700 (PDT) Date: Thu, 25 Aug 2022 13:06:00 -0700 From: Nathan Bossart To: talk to ben Cc: Tom Lane , Alvaro Herrera , Robert Haas , "Bossart, Nathan" , David Steele , Fujii Masao , "pgsql-hackers@postgresql.org" , Michael Paquier , Magnus Hagander , Stephen Frost Subject: Re: archive modules Message-ID: <20220825200600.GA1465148@nathanxps13> References: <20220707151157.cakxxwwadchkov35@alvherre.pgsql> <2985823.1657208900@sss.pgh.pa.us> <20220707165908.GB2251016@nathanxps13> <20220823173930.GB1207981@nathanxps13> <727557.1661276860@sss.pgh.pa.us> <20220824221723.GA1347845@nathanxps13> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="n8g4imXOkfNTN/H1" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --n8g4imXOkfNTN/H1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Aug 25, 2022 at 03:29:41PM +0200, talk to ben wrote: > Here is a patch with the proposed wording. Here is the same patch with a couple more links. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com --n8g4imXOkfNTN/H1 Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="v4-0001-basic_archive-parameter-visibility-doc-patch.patch" From 92a6d8669d9e5b527a7ac9af7eb359a86526775b Mon Sep 17 00:00:00 2001 From: benoit Date: Mon, 22 Aug 2022 12:00:46 +0200 Subject: [PATCH v4 1/1] basic_archive parameter visibility doc patch Module parameters are only visible from the pg_settings view once the module is loaded. Since an archive module is loaded by the archiver process, the parameters are never visible from the view. This patch adds a note bout this in the pg_settings system view documentation. --- doc/src/sgml/system-views.sgml | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/doc/src/sgml/system-views.sgml b/doc/src/sgml/system-views.sgml index 44aa70a031..18ac4620f0 100644 --- a/doc/src/sgml/system-views.sgml +++ b/doc/src/sgml/system-views.sgml @@ -3275,7 +3275,15 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx This view does not display customized options - until the extension module that defines them has been loaded. + until the extension module that defines them has been loaded by the backend + process executing the query (e.g., via + , the + LOAD command, or a call + to a user-defined C function). For example, + since the 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. -- 2.25.1 --n8g4imXOkfNTN/H1--