Re: Postgres 12: backend crashes when creating non-deterministic collation

From: Thomas Kellerer <spam_eater(at)gmx(dot)net>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Postgres 12: backend crashes when creating non-deterministic collation
Date: 2019-10-04 14:21:26
Message-ID: ac33f189-2bcd-3be6-1dee-cb44c34ddb20@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Laurenz Albe schrieb am 04.10.2019 um 16:04:
>> I was trying to learn how the new non-deterministic collations in v12
>> work, but the following makes the backend crash:
>>
>> CREATE COLLATION de_ci (provider = icu, locale = 'de-x-icu',
>> deterministic = false);
>>
>> Which leads to:
>>
>> 2019-10-04 11:54:23 CEST LOG: server process (PID 7540) was
>> terminated by exception 0xC0000005
>>
>> I might have misunderstood how to use deterministic to create a case-
>> insensitive collation, but I don't think the backend should crash if
>> I do something wrong ;)
>
> Yes, there is a bug somewhere. FWIW, it works on my Linux system.

It also works on Windows when I specify "correct" locale names - the above seems to be an edge case.
Is it worth the effort to report that through the bug reporting form?

> To get a case insensitive collation you'd have to use something like
>
> LOCALE = 'de-DE-u-ks-level2'

Creating works, but apparently on Windows ICU does not support this.

The following works fine on Linux (returns both rows), but not on Windows (returns nothing)

create collation de_ci (provider = icu, locale = 'de-DE-u-ks-level2', deterministic = false);
create table test (name text);
insert into test values ('FOO'), ('Foo');

select *
from test
where name = 'foo' collate de_ci;

Not a big deal, but might surprise some people.

Thomas

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Christoph Moench-Tegeder 2019-10-04 14:29:32 Re: Perl DBI converts UTF-8 again to UTF-8 before sending it to the server
Previous Message Josef Šimánek 2019-10-04 14:13:57 Re: Clarification on the release notes of postgresql 12 regarding pg_upgrade