Re: ERROR: new collation (en_US.UTF-8) is incompatible with the collation of the template database (en_US.utf-8) - Mailing list pgsql-general

From Tomas Pospisek
Subject Re: ERROR: new collation (en_US.UTF-8) is incompatible with the collation of the template database (en_US.utf-8)
Date
Msg-id 23557e37-b480-2125-1afd-8f7fc26c1b09@sourcepole.ch
Whole thread Raw
In response to Re: ERROR: new collation (en_US.UTF-8) is incompatible with the collation of the template database (en_US.utf-8)  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
On 23.06.22 20:21, Adrian Klaver wrote:
> On 6/23/22 10:11, Adrian Klaver wrote:
>> 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').
> 
> Well that was clear as mud.

:-D

> My point was that I don't see why the end 
> user should have to do this when it could be handled internally in the 
> pg_restore code.

That would indeed be very friendly of pg_restore if it'd take that 
little task off the user :-)

+1 of course :-)

*t



pgsql-general by date:

Previous
From: "Daniel Verite"
Date:
Subject: Re: Differences in Escaped bytea's when creating a plain pg_dump
Next
From: Peter Eisentraut
Date:
Subject: Re: ERROR: new collation (en_US.UTF-8) is incompatible with the collation of the template database (en_US.utf-8)