Open bcomnes opened 10 months ago
I followed the suggestions here: https://dba.stackexchange.com/questions/324649/collation-version-mismatch
This is pretty unfortunate and has to do with the transition to bookworm: https://github.com/fly-apps/postgres-flex/pull/205
We should be able to detect and address collation issues on boot then work to reindex things concurrently. Given how we roll things out though, the primary would be the last node to be upgraded so we wouldn't be able to avoid these errors completely. However, they would be cleared by the end of the upgrade process. Not deal, but it's better than leaving the collation issues for the user to address.
After updating from v0.0.42 to v0.0.43 with fly image update, my database started spamming the following warning:
Any suggestions on how to address this?