Re: ltree_gist indexes broken after pg_upgrade from 12 to 13
От | Andres Freund |
---|---|
Тема | Re: ltree_gist indexes broken after pg_upgrade from 12 to 13 |
Дата | |
Msg-id | 20220224220658.5l6u4lkfyxi5lfgl@alap3.anarazel.de обсуждение исходный текст |
Ответ на | ltree_gist indexes broken after pg_upgrade from 12 to 13 (Tomas Vondra <tomas.vondra@enterprisedb.com>) |
Ответы |
Re: ltree_gist indexes broken after pg_upgrade from 12 to 13
|
Список | pgsql-hackers |
Hi, On 2022-02-24 22:15:20 +0100, Tomas Vondra wrote: > After thinking about this I only see two options: > > 1) Don't apply the patch and tell everyone using ltree_gist they need to > rebuild the index after pg_upgrade from 12 to 13+. The downside of this > is larger indexes (because some tuples are 20B larger). > > 2) Apply the patch + tell those who already upgraded from 12 to rebuild > ltree_gist indexes, because those might be broken due to new inserts. > > > My opinion is to do (2), because at least those who'll upgrade later > (which is a lot of people) will be fine without a rebuild. And it also > makes the indexes a bit smaller, thanks to saving 20B. Won't 2) also break indexes created without a pg_upgrade? "already upgraded from 12" sounds like it wouldn't but I don't see why? Greetings, Andres Freund
В списке pgsql-hackers по дате отправления: