I got collation warnings on postgresql, each time libicu is updated I think. I know how…
- User
I got collation warnings on postgresql, each time libicu is updated I think. I know how to rebuild the three databases I have when that happens, but it's a bit boring, I'd like a permanent solution..
Assistant
PostgreSQL's collation warnings after libicu updates are indeed annoying. For a more permanent solution, you could:
-
Use version-independent collations by adding the suffix "und-u-ks-level2" to your collation specifications (available in PostgreSQL 12+)
-
Create a simple automation script that runs after system updates to detect and rebuild affected databases
-
Configure your package manager to hold the libicu package at a specific version to prevent automatic updates
The version-independent approach is generally the most robust solution if compatible with your use case, as it avoids the underlying problem entirely rather than just making rebuilds easier.
-
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.