Re: ERROR: new collation (en_US.UTF-8) is incompatible with the collation of the template database (en_US.utf-8)
От | Adrian Klaver |
---|---|
Тема | Re: ERROR: new collation (en_US.UTF-8) is incompatible with the collation of the template database (en_US.utf-8) |
Дата | |
Msg-id | 3370e253-1928-294a-facb-e9850bfefa90@aklaver.com обсуждение исходный текст |
Ответ на | Re: ERROR: new collation (en_US.UTF-8) is incompatible with the collation of the template database (en_US.utf-8) (Tomas Pospisek <tpo2@sourcepole.ch>) |
Ответы |
Re: ERROR: new collation (en_US.UTF-8) is incompatible with the collation of the template database (en_US.utf-8)
|
Список | pgsql-general |
On 6/23/22 00:37, Tomas Pospisek wrote: > On 22.06.22 22:18, Tomas Pospisek wrote: >> On 22.06.22 21:25, Adrian Klaver wrote: >>> On 6/22/22 12:17, Tomas Pospisek wrote: > > So I used both pg_dump and pg_restore from the newer machine. Result is > still the same. So I'll use Tom Lane's suggestion too and fix the > 'UTF-8' spelling in the dump file: Not sure why that is necessary? Is seems this is low hanging fruit that could dealt with by the equivalent of lower('en_US.UTF-8') = lower('en_US.utf-8'). > > Tom Lane wrote: > > > This is probably more about dumping from different operating systems. > > The spelling of the locale name is under the control of the OS, > > and Postgres doesn't know very much about the semantics of it > > (so I think we conservatively assume that any difference in > > spelling is significant). > > > > Best bet might be to edit the dump file to adjust the locale > > spellings to match your new system. > > Many thanks to both Tom & Adrian!!! > *t > > -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: