From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Andres Freund <andres@anarazel.de>
Cc: Wyatt Alt <wyatt.alt@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: cache lookup failed dropping public schema with trgm index
Date: Mon, 21 Aug 2023 19:27:19 -0400
Message-ID: <2983696.1692660439@sss.pgh.pa.us> (raw)
In-Reply-To: <ZOPrYNyJO95YItPp@paquier.xyz>
References: <CAGem3qAM7M7B3DdccpgepRxuoKPd2Y74qJ5NSNRjLiN21dPhgg@mail.gmail.com>
<20230821223610.glmwmdsv2xofihiu@awork3.anarazel.de>
<ZOPrYNyJO95YItPp@paquier.xyz>
Michael Paquier <michael@paquier.xyz> writes:
> On Mon, Aug 21, 2023 at 03:36:10PM -0700, Andres Freund wrote:
>> It also seems to work without even involving a drop schema. Just dropping
>> pg_trgm with cascade is sufficient.
> FWIW, after a bisect I can see that 911e7020 is the origin of the
> failure (`git bisect start b5d69b7 9e1c9f9` based on two merge-bases).
Hmm. I see that 911e7020 modified pg_trgm's install script with
+ALTER OPERATOR FAMILY gist_trgm_ops USING gist
+ADD FUNCTION 10 (text) gtrgm_options (internal);
I wonder whether that correctly adds a dependency to ensure the
opfamily is dropped before the function.
regards, tom lane
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: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, michael@paquier.xyz, andres@anarazel.de, wyatt.alt@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: cache lookup failed dropping public schema with trgm index
In-Reply-To: <2983696.1692660439@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox