Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uokEc-009QU8-6s for pgsql-general@arkaria.postgresql.org; Wed, 20 Aug 2025 14:56:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uokEa-008xgg-EP for pgsql-general@arkaria.postgresql.org; Wed, 20 Aug 2025 14:56:17 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uokEa-008xgX-3a for pgsql-general@lists.postgresql.org; Wed, 20 Aug 2025 14:56:16 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uokEW-000rWm-26 for pgsql-general@lists.postgresql.org; Wed, 20 Aug 2025 14:56:15 +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 57KEu6XD1020134; Wed, 20 Aug 2025 10:56:06 -0400 From: Tom Lane To: Adrian Klaver cc: Achilleas Mantzios , "pgsql-general@lists.postgresql.org" Subject: Re: pg_upgrade from 18beta1 -> 18beta3 - problem with btree_gist contrib module / extension In-reply-to: <54d352ad-3f64-4492-aaaf-1ebaeac5471c@aklaver.com> References: <4d301501-9985-4e68-b1c1-2360c251048c@cloud.gatewaynet.com> <54d352ad-3f64-4492-aaaf-1ebaeac5471c@aklaver.com> Comments: In-reply-to Adrian Klaver message dated "Wed, 20 Aug 2025 07:39:06 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1020132.1755701766.1@sss.pgh.pa.us> Date: Wed, 20 Aug 2025 10:56:06 -0400 Message-ID: <1020133.1755701766@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Adrian Klaver writes: > I can not find gist_stratnum_btree in: > https://www.postgresql.org/docs/18/btree-gist.html > or in the source. > How did it end up in the database? See commit 32edf732e. Perhaps that renaming should not have been done post-beta1, but that's where we are. regards, tom lane