public inbox for [email protected]  

help / color / mirror / Atom feed

From: Paul A Jungwirth <[email protected]>
To: Adrian Klaver <[email protected]>
Cc: Achilleas Mantzios <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: pg_upgrade from 18beta1 -> 18beta3 - problem with btree_gist contrib module / extension
Date: Wed, 20 Aug 2025 09:49:31 -0500
Message-ID: <CA+renyU=3z2J_yLaz1BFk9sHeO1Gnu=KMof5vcb-diW1_JZggQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

On Wed, Aug 20, 2025 at 9:39 AM Adrian Klaver <[email protected]> wrote:
>
> 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?

gist_stratnum_btree was in beta1 but was renamed to
gist_translate_cmptype_btree by
32edf732e8dc9eb3e7a923aeb67d49246744a20a.

> > 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?

That seems like the easiest fix to me. But if you've built indexes
based on those opclasses then more work is required, as here.

I don't know what pg_upgrade tries to support for moving from one beta
release to another. Is this something we should try to fix?

Yours,

-- 
Paul              ~{:-)
[email protected]

view thread (5+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: pg_upgrade from 18beta1 -> 18beta3 - problem with btree_gist contrib module / extension
  In-Reply-To: <CA+renyU=3z2J_yLaz1BFk9sHeO1Gnu=KMof5vcb-diW1_JZggQ@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox