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 1oQY0W-0005kT-92 for pgsql-hackers@arkaria.postgresql.org; Tue, 23 Aug 2022 17:48:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oQY0U-0005Jt-JQ for pgsql-hackers@arkaria.postgresql.org; Tue, 23 Aug 2022 17:48:06 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oQY0U-0005Jj-A7 for pgsql-hackers@lists.postgresql.org; Tue, 23 Aug 2022 17:48:06 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oQY0P-0002qN-DX for pgsql-hackers@postgresql.org; Tue, 23 Aug 2022 17:48:03 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 27NHleUN727558; Tue, 23 Aug 2022 13:47:40 -0400 From: Tom Lane To: Nathan Bossart cc: talk to ben , Alvaro Herrera , Robert Haas , "Bossart, Nathan" , David Steele , Fujii Masao , "pgsql-hackers@postgresql.org" , Michael Paquier , Magnus Hagander , Stephen Frost Subject: Re: archive modules In-reply-to: <20220823173930.GB1207981@nathanxps13> References: <20220707151157.cakxxwwadchkov35@alvherre.pgsql> <2985823.1657208900@sss.pgh.pa.us> <20220707165908.GB2251016@nathanxps13> <20220823173930.GB1207981@nathanxps13> Comments: In-reply-to Nathan Bossart message dated "Tue, 23 Aug 2022 10:39:30 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <727556.1661276860.1@sss.pgh.pa.us> Date: Tue, 23 Aug 2022 13:47:40 -0400 Message-ID: <727557.1661276860@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Nathan Bossart writes: > I don't know if it makes sense to document this in basic_archive. On one > hand, it seems like folks will commonly encounter this behavior with this > module, so this feels like a natural place for such a note. But on the > other hand, this is generic behavior for any library that is dynamically > loaded in a separate process. Yeah, I don't think this material is at all specific to basic_archive. Maybe it could be documented near the relevant views, if it isn't already. Also, I think the proposed text neglects the case of including the module in shared_preload_libraries. regards, tom lane