From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Tomas Pospisek <tpo2(at)sourcepole(dot)ch>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: ERROR: new collation (en_US.UTF-8) is incompatible with the collation of the template database (en_US.utf-8) |
Date: | 2022-06-23 17:11:21 |
Message-ID: | 3370e253-1928-294a-facb-e9850bfefa90@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2022-06-23 18:21:21 | Re: ERROR: new collation (en_US.UTF-8) is incompatible with the collation of the template database (en_US.utf-8) |
Previous Message | WR | 2022-06-23 16:21:37 | Re: Differences in Escaped bytea's when creating a plain pg_dump |