Re: Q: documentation improvement re collation version mismatch
От | Ron |
---|---|
Тема | Re: Q: documentation improvement re collation version mismatch |
Дата | |
Msg-id | 3515c6ba-0487-1ead-ef3d-84541767f370@gmail.com обсуждение исходный текст |
Ответ на | Re: Q: documentation improvement re collation version mismatch (Julien Rouhaud <rjuju123@gmail.com>) |
Ответы |
Re: Q: documentation improvement re collation version mismatch
|
Список | pgsql-general |
On 11/10/22 08:33, Julien Rouhaud wrote: > On Thu, Nov 10, 2022 at 08:04:37AM -0600, Ron wrote: >> On 11/10/22 02:33, Julien Rouhaud wrote: >> [snip] >>> For now, the only safe way to go is either reindex everything, or everything >>> except some safe cases (non-partial indexes on plain-non-collatable datatypes >>> only). Usually, those safe cases are usually enough to avoid most of useless >>> reindex activity. >> In this situation, I queried for all indices with text-type columns >> (including UUID) and reindexed them. > That may work in your personal use case, but it's not generally safe. I hope > you don't have partial indexes, Aren't partial indices listed in pg_indexes? > expressions or functions that internally relied > on collatable datatypes, No such indices. > or indexes on other plain collatable datatypes. What other data types besides the text types are collatable? -- Angular momentum makes the world go 'round.
В списке pgsql-general по дате отправления: