| From: | Richard van der Hoff <richard(at)matrix(dot)org> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Inexplicable duplicate rows with unique constraint |
| Date: | 2020-01-16 17:31:38 |
| Message-ID: | 9265a081-adfd-4792-5385-70cc09a39baa@matrix.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 16/01/2020 17:27, Adrian Klaver wrote:
> On 1/16/20 9:24 AM, Richard van der Hoff wrote:
>>
>> It seems like a plausible explanation but it's worth noting that all
>> the indexed data here is (despite being in text columns), plain ascii.
>> I'm surprised that a change in collation rules would change the
>> sorting of such strings, and hence that it could lead to this problem.
>> Am I naive?
>
> In psql who does:
>
> \l the_database_name
>
> show?
synapse=> \l synapse
List of databases
Name | Owner | Encoding | Collate | Ctype | Access
privileges
---------+----------+----------+-------------+-------------+-----------------------
synapse | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
postgres=CTc/postgres+
| | | | |
=Tc/postgres +
| | | | |
synapse=CTc/postgres
(1 row)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-01-16 17:48:06 | Re: Inexplicable duplicate rows with unique constraint |
| Previous Message | Richard van der Hoff | 2020-01-16 17:28:46 | Re: Inexplicable duplicate rows with unique constraint |