From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Add standard collation UNICODE |
Date: | 2023-05-12 08:04:50 |
Message-ID: | 30864847-fab1-268c-60c3-b50be4d9f503@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 08.05.23 17:48, Peter Eisentraut wrote:
> On 27.04.23 13:44, Daniel Verite wrote:
>> This collation has an empty pg_collation.collversion column, instead
>> of being set to the same value as "und-x-icu" to track its version.
>
>> The original patch implements this as an INSERT in which it would be
>> easy to
>> fix I guess, but in current HEAD it comes as an entry in
>> include/catalog/pg_collation.dat:
>>
>> { oid => '963',
>> descr => 'sorts using the Unicode Collation Algorithm with default
>> settings',
>> collname => 'unicode', collprovider => 'i', collencoding => '-1',
>> colliculocale => 'und' },
>>
>> Should it be converted back into an INSERT or better left
>> in this file and collversion being updated afterwards?
>
> How about we do it with an UPDATE command. We already do this for
> pg_database in a similar way. See attached patch.
This has been committed.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2023-05-12 08:28:00 | Re: BUG: Postgres 14 + vacuum_defer_cleanup_age + FOR UPDATE + UPDATE |
Previous Message | Alvaro Herrera | 2023-05-12 07:46:51 | Re: psql tests hangs |