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

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, 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-24 11:21:45
Message-ID: 1c22da3e-1b18-39b8-cecb-26777dc683f0@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 23.06.22 20:21, Adrian Klaver wrote:
>> 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. 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.

There are also cases where on one system the locale is spelled
xx_YY.UTF8 and on another xx_YY.UTF-8. If we start adjusting for case,
should we adjust for this as well? What other cases are there?

So this would need a bit more research.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Mahendrakar, Prabhakar - Dell Team 2022-06-24 13:03:57 RE: Postgresql error : PANIC: could not locate a valid checkpoint record
Previous Message Amit Kapila 2022-06-24 10:19:24 Re: Support logical replication of DDLs