Unsupported locale #48
Replies: 4 comments
-
|
Just include i.e. |
Beta Was this translation helpful? Give feedback.
-
|
Does not work here. |
Beta Was this translation helpful? Give feedback.
-
|
I just realized that I misread your logs. Basically, postgresql tells you that your database was initialized with an unknown LC_COLLATE value, which was set to "utf-8" (instead of i.e. C or C.UTF-8). To my knowledge, there's now way to get that right after creation. So before upgrading your database, you will have to drop the old database, create a new one and update your new one with your old data. Follow i.e. this tutorial. Afterwards you should be able to update to a new version using this dockerized solution. Sorry again for this confusion! My provided solution only works if you created a database with known locale settings. |
Beta Was this translation helpful? Give feedback.
-
|
hi, i'm facing a similar problem that should be fixed by the script you suggested, but it seems that POSTGRES_INITDB_ARGS is ignored. setting PG_LOCALE as en_US.utf8, this is my scirpt: thank you for your support. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
While trying to migrate a 9.6.11-alpine db to 13, I receive the following error:
This is the locale / collation of the old db:
CREATE DATABASE xx WITH TEMPLATE = template0 ENCODING = 'UTF8' LC_COLLATE = 'utf-8' LC_CTYPE = 'UTF-8';Beta Was this translation helpful? Give feedback.
All reactions