| From: | Christoph Berg <myon(at)debian(dot)org> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Collation versioning |
| Date: | 2018-09-13 08:22:36 |
| Message-ID: | 20180913082236.GB13439@msg.df7cb.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Re: Peter Eisentraut 2018-09-13 <4f60612c-a7b5-092d-1532-21ff7a106bd5(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergei Kornilov | 2018-09-13 09:00:49 | Re: Indicate anti-wraparound autovacuum in log_autovacuum_min_duration |
| Previous Message | Michael Paquier | 2018-09-13 08:03:28 | Re: Unused argument from execute_sql_string() |