| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Wyatt Alt <wyatt(dot)alt(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: cache lookup failed dropping public schema with trgm index |
| Date: | 2023-08-21 23:27:19 |
| Message-ID: | 2983696.1692660439@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Michael Paquier <michael(at)paquier(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2023-08-22 01:43:59 | Re: cache lookup failed dropping public schema with trgm index |
| Previous Message | Wyatt Alt | 2023-08-21 23:13:57 | Re: cache lookup failed dropping public schema with trgm index |