Re: could not determine encoding for locale "et_EE.UTF-8": codeset is "CPUTF-8" in pg_restore
От | Tom Lane |
---|---|
Тема | Re: could not determine encoding for locale "et_EE.UTF-8": codeset is "CPUTF-8" in pg_restore |
Дата | |
Msg-id | 22672.1585442578@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | could not determine encoding for locale "et_EE.UTF-8": codeset is "CPUTF-8" in pg_restore ("Andrus" <kobruleht2@hot.ee>) |
Ответы |
Re: could not determine encoding for locale "et_EE.UTF-8": codeset is "CPUTF-8" in pg_restore
Re: could not determine encoding for locale "et_EE.UTF-8": codeset is "CPUTF-8" in pg_restore |
Список | pgsql-general |
"Andrus" <kobruleht2@hot.ee> writes: > Postgres 12 database dump is created in Debian 10 using pg_dump . > Trying to restore it in Windows 10 using > pg_restore --clean --create --if-exists --dbname=postgres --jobs=8 --no-password > mydb.backup > produces strange message > pg_restore: WARNING: could not determine encoding for locale "et_EE.UTF-8": > codeset is "CPUTF-8" > How to fix this ? Generally speaking, locale names from Unix systems won't work at all on Windows. You need to create the database manually with whatever seems to be the closest Windows locale match, and then restore its contents without using --create. (I do agree that that message isn't the most helpful thing. It looks like chklocale.c is overoptimistically assuming that what it's handed is valid, even if GetLocaleInfoEx says it isn't.) regards, tom lane
В списке pgsql-general по дате отправления: