| From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
|---|---|
| To: | "Karsten Hilbert" <Karsten(dot)Hilbert(at)gmx(dot)net> |
| Cc: | "Christophe Pettus" <xof(at)thebuild(dot)com>,pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Q: fixing collation version mismatches |
| Date: | 2022-11-14 16:42:16 |
| Message-ID: | 206a0d6b-d91d-4fc9-a467-2bcf426fed06@manitou-mail.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Karsten Hilbert wrote:
> Which is why my question still stands: does the above
> three-strikes operation safely take care of any collation
> issues that may currently exist in a database ?
For the indexes, yes, but theorically, all constraints involving collatable
types need a recheck.
For foreign key constraints with non-deterministic collations, there
might be equality tests that pass with an older Unicode version and fail
with a newer Unicode version.
For check constraints as well, checks applied to strings with recent
Unicode characters can give different results after an upgrade.
Best regards,
--
Daniel Vérité
https://postgresql.verite.pro/
Twitter: @DanielVerite
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karsten Hilbert | 2022-11-14 17:31:43 | Re: Q: fixing collation version mismatches |
| Previous Message | Upesh Desai | 2022-11-14 16:30:30 | Phantom Permissions Error |