From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Oleg Tselebrovskiy <o(dot)tselebrovskiy(at)postgrespro(dot)ru>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PROPOSAL] Skip test citext_utf8 on Windows |
Date: | 2024-03-12 01:55:53 |
Message-ID: | ef4a2dc9-c981-bfc5-e5aa-7249b5979a7c@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2024-03-11 Mo 04:21, Oleg Tselebrovskiy wrote:
> Greetings, everyone!
>
> While running "installchecks" on databases with UTF-8 encoding the test
> citext_utf8 fails because of Turkish dotted I like this:
>
> SELECT 'i'::citext = 'İ'::citext AS t;
> t
> ---
> - t
> + f
> (1 row)
>
> I tried to replicate the test's results by hand and with any collation
> that I tried (including --locale="Turkish") this test failed
>
> Also an interesing result of my tesing. If you initialize you DB
> with -E utf-8 --locale="Turkish" and then run select LOWER('İ');
> the output will be this:
> lower
> -------
> İ
> (1 row)
>
> Which I find strange since lower() uses collation that was passed
> (default in this case but still)
Wouldn't we be better off finding a Windows fix for this, instead of
sweeping it under the rug?
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2024-03-12 02:20:18 | Re: [PoC] Improve dead tuple storage for lazy vacuum |
Previous Message | Andrew Dunstan | 2024-03-12 01:43:33 | Re: WIP Incremental JSON Parser |