Re: Collation versioning
| От | Christoph Berg |
|---|---|
| Тема | Re: Collation versioning |
| Дата | |
| Msg-id | 20180913082236.GB13439@msg.df7cb.de обсуждение исходный текст |
| Ответ на | Re: Collation versioning (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>) |
| Ответы |
Re: Collation versioning
|
| Список | pgsql-hackers |
Re: Peter Eisentraut 2018-09-13 <4f60612c-a7b5-092d-1532-21ff7a106bd5@2ndquadrant.com> > Moreover, the fix for a collation version mismatch is, in the simplest > case, to go around and REINDEX everything. Making the collation or > collation version global doesn't fix that. It would actually make it > harder because you couldn't run ALTER COLLATION REFRESH VERSION until > after you have rebuilt all affected objects *in all databases*. Btw, I think a "reindexdb --all --collation" (and the SQL per-database equivalent) that only rebuilds indexes that are affected by collations would be immensely useful to have. Christoph
В списке pgsql-hackers по дате отправления: