Re: cache lookup failed dropping public schema with trgm index
От | Tom Lane |
---|---|
Тема | Re: cache lookup failed dropping public schema with trgm index |
Дата | |
Msg-id | 2983696.1692660439@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: cache lookup failed dropping public schema with trgm index (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: cache lookup failed dropping public schema with trgm index
Re: cache lookup failed dropping public schema with trgm index |
Список | pgsql-bugs |
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
В списке pgsql-bugs по дате отправления: