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 1pedMZ-0003q8-1Y for pgsql-hackers@arkaria.postgresql.org; Tue, 21 Mar 2023 14:53:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pedLY-0002C5-5W for pgsql-hackers@arkaria.postgresql.org; Tue, 21 Mar 2023 14:52:20 +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 1pedLX-0002AT-SO for pgsql-hackers@lists.postgresql.org; Tue, 21 Mar 2023 14:52:19 +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 1pedLV-0007cd-E3 for pgsql-hackers@lists.postgresql.org; Tue, 21 Mar 2023 14:52:19 +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 32LEqBFJ1219581; Tue, 21 Mar 2023 10:52:11 -0400 From: Tom Lane To: "Regina Obe" cc: "'Sandro Santilli'" , "'Gregory Stark \(as CFM\)'" , pgsql-hackers@lists.postgresql.org Subject: Re: Ability to reference other extensions by schema in extension scripts In-reply-to: <007601d95c01$95744cd0$c05ce670$@pcorp.us> References: <005401d95083$26ca24a0$745e6de0$@pcorp.us> <995823.1678478825@sss.pgh.pa.us> <004b01d95394$16123ee0$4236bca0$@pcorp.us> <1012975.1678486476@sss.pgh.pa.us> <005501d953a0$906c4df0$b144e9d0$@pcorp.us> <1019515.1678488437@sss.pgh.pa.us> <001d01d953f2$099b6430$1cd22c90$@pcorp.us> <20230313115916.ivvg4tj54szeu5rj@c19> <000701d955f6$dfaaf8a0$9f00e9e0$@pcorp.us> <20230316101418.2a32erangr3nvnuk@c19> <1103862.1679352440@sss.pgh.pa.us> <007601d95c01$95744cd0$c05ce670$@pcorp.us> Comments: In-reply-to "Regina Obe" message dated "Tue, 21 Mar 2023 10:29:44 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1219579.1679410331.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Tue, 21 Mar 2023 10:52:11 -0400 Message-ID: <1219580.1679410331@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "Regina Obe" writes: >> making the no_relocate values visible somehow, I'm not convinced that >> pg_available_extension_versions should be the place to do it. ISTM wha= t's >> relevant is the no_relocate values of *installed* extensions, not those= of >> potentially-installable extensions. If we had a view over pg_extension= then >> that might be a place to add this, but we don't. On the whole it didn'= t seem >> important enough to pursue, so I just left it out. > Thanks. Agree with get_available_versions_for_extension, not necessary. If we did feel like doing something about this, on reflection I think the thing to do would be to add no_relocate as an actual column in pg_extension, probably of type "oid[]". Then we could modify the SET SCHEMA code to check that instead of parsing the extension control files. That'd be a little cleaner, but I can't say that I'm hugely excited about it. regards, tom lane