Re: Issues with inconsistent COLLATION installation - Mailing list pgsql-general

From Tom Lane
Subject Re: Issues with inconsistent COLLATION installation
Date
Msg-id 3361.1568060977@sss.pgh.pa.us
Whole thread Raw
In response to Re: Issues with inconsistent COLLATION installation  (Cory Nemelka <cnemelka@gmail.com>)
List pgsql-general
Cory Nemelka <cnemelka@gmail.com> writes:
> Here is encoding for existing database:
>                                   List of databases
> ┌───────────┬──────────┬──────────┬─────────────┬─────────────┬───────────────────────┐
> │   Name    │  Owner   │ Encoding │   Collate   │    Ctype    │   Access
> privileges   │
> ├───────────┼──────────┼──────────┼─────────────┼─────────────┼───────────────────────┤
> │ thedatabase │ postgres │ UTF8     │ en_US.UTF-8 │ en_US.UTF-8 │
>             │

Hmm.  It's interesting that the collate/ctype locales say "UTF-8"
where locale -a says "utf8".  It's not apparent to me what relation
that might have to your observed problem, but it suggests that
this cluster doesn't exactly have a pristine history.  Did you
perhaps try to move the data files from one platform to another?

            regards, tom lane



pgsql-general by date:

Previous
From: Cory Nemelka
Date:
Subject: Re: Issues with inconsistent COLLATION installation
Next
From: "Daniel Verite"
Date:
Subject: Re: Issues with inconsistent COLLATION installation