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 1uojy4-009LNw-Ag for pgsql-general@arkaria.postgresql.org; Wed, 20 Aug 2025 14:39:13 +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 1uojy3-008qBf-PS for pgsql-general@arkaria.postgresql.org; Wed, 20 Aug 2025 14:39:12 +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 1uojy2-008qBV-QE for pgsql-general@lists.postgresql.org; Wed, 20 Aug 2025 14:39:12 +0000 Received: from fout-a1-smtp.messagingengine.com ([103.168.172.144]) by makus.postgresql.org with smtp (Exim 4.96) (envelope-from ) id 1uojy0-000rPk-2P for pgsql-general@lists.postgresql.org; Wed, 20 Aug 2025 14:39:10 +0000 Received: from phl-compute-12.internal (phl-compute-12.internal [10.202.2.52]) by mailfout.phl.internal (Postfix) with ESMTP id 21AE0EC0519; Wed, 20 Aug 2025 10:39:08 -0400 (EDT) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-12.internal (MEProxy); Wed, 20 Aug 2025 10:39:08 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1755700748; x=1755787148; bh=4CYU+97kdiUgoCVVOsyHdUoAsxDrLIZ8YPRN8PSByRo=; b= VfpaJdWsuVTzsGU27LTWO14rtY7ZJljifnAYBp9SyBg77vXEKKf96FTVGM71QXYW vtN3DsxpBhYhWgVlCr99Umq+7el4H4+X1a0NM1j6vrnoXjmTMHk3IHc7aSFgny85 hWpiSb2YjLVxgNZbNeCkqwPDe/i8lhRSp0cbIYApiSYJu/VmRUFGDK33o0KS9cPU ACoJmHHDNfF2nGNZNiMeZ5GFenPEmHzVtBjBjXeMjLRLvDjmwrRmN6/fju68U9PV NQx8y4SSNjkcfumLrL9bNFJ3SXMGVW5W8zdtoEqeJ/pAq2qUlBLCmBJrGLmXl566 jCgzLS20nE6snibuljNQXw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; t=1755700748; x=1755787148; bh=4 CYU+97kdiUgoCVVOsyHdUoAsxDrLIZ8YPRN8PSByRo=; b=irajQBXlfzIeHHRBm h4lsE2QbOfrGcMuNX4vFBEBEcJn6uaanyFS+HG61JaCFsrvYAQjwXcofgkUz73+i W0oi0d5poxHA45r70Qv71OUr3GUlj3qcjXgb4Xp47gtbMN+x3HpG1l6R1iBUMvQt pBmolZHuyBe26QoGFZ+m8OLMxRPImt8JwTliN8sj2pOIhQbvqC7KtFLIh6glrqyI Kqvv2dxj705pArPSoJpGNzGCYHbzOWlpOlLCgmvBUf4fM7cNAVqKF5bZHz1yJN8w UAt1Rxs+Yw++4P7rVcTH4jvLWIgy6xFYxx/+JV8+eO/Qux4IxIv2lY3NnXsuADXC 16rtQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdefgdduheekiedvucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujf gurhepkfffgggfuffvfhfhjggtgfesthekredttddvjeenucfhrhhomheptegurhhirghn ucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhmqe enucggtffrrghtthgvrhhnpeelgeevkeekkeeuiefgtdevieeluefhfedufeetkeejffek jeeujeehgeehgeektdenucffohhmrghinhepphhoshhtghhrvghsqhhlrdhorhhgnecuve hluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhirghn rdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomhdpnhgspghrtghpthhtohepvddpmhhoug gvpehsmhhtphhouhhtpdhrtghpthhtoheprgdrmhgrnhhtiihiohhssegtlhhouhgurdhg rghtvgifrgihnhgvthdrtghomhdprhgtphhtthhopehpghhsqhhlqdhgvghnvghrrghlse hlihhsthhsrdhpohhsthhgrhgvshhqlhdrohhrgh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 20 Aug 2025 10:39:07 -0400 (EDT) Message-ID: <54d352ad-3f64-4492-aaaf-1ebaeac5471c@aklaver.com> Date: Wed, 20 Aug 2025 07:39:06 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: pg_upgrade from 18beta1 -> 18beta3 - problem with btree_gist contrib module / extension To: Achilleas Mantzios , "pgsql-general@lists.postgresql.org" References: <4d301501-9985-4e68-b1c1-2360c251048c@cloud.gatewaynet.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: <4d301501-9985-4e68-b1c1-2360c251048c@cloud.gatewaynet.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 8/20/25 05:50, Achilleas Mantzios wrote: > pg_restore: from TOC entry 4295; 1255 596569951 FUNCTION > gist_stratnum_btree(integer) postgres > pg_restore: error: could not execute query: ERROR:  could not find > function "gist_stratnum_btree" in file "/usr/local/pgsql/lib/btree_gist.so" > Command was: CREATE FUNCTION "public"."gist_stratnum_btree"(integer) > RETURNS smallint >    LANGUAGE "c" IMMUTABLE STRICT PARALLEL SAFE >    AS '$libdir/btree_gist', 'gist_stratnum_btree'; 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? > > > The solution was to somehow restart 18beta1, drop btree_gist and all its > dependent constraints / indexes / objects , pg_upgrade and finally re- > create extension and dependent objects. > Something more then DROP EXTENSION/CREATE EXTENSION btree_gist? -- Adrian Klaver adrian.klaver@aklaver.com