From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Cory Nemelka <cnemelka(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Issues with inconsistent COLLATION installation |
Date: | 2019-09-09 20:29:37 |
Message-ID: | 3361.1568060977@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Cory Nemelka <cnemelka(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Verite | 2019-09-09 20:46:29 | Re: Issues with inconsistent COLLATION installation |
Previous Message | Cory Nemelka | 2019-09-09 20:08:04 | Re: Issues with inconsistent COLLATION installation |