Re: Add standard collation UNICODE

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add standard collation UNICODE
Date: 2023-03-23 20:16:35
Message-ID: bae737e593b8768a5dde3762741c17b599b71ab8.camel@j-davis.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 2023-03-09 at 11:23 -0800, Jeff Davis wrote:
> Looks good to me.

Another thought: for ICU, do we want the default collation to be
UNICODE (root collation)? What we have now gets the default from the
environment, which is consistent with the libc provider.

But now that we have the UNICODE collation, it makes me wonder if we
should just default to that. The server's environment doesn't
necessarily say much about the locale of the data stored in it or the
locale of the applications accessing it.

I don't have a strong opinion here, but I thought I'd raise the issue.

By my count, >50% of locales are actually just the root locale. I'm not
sure if that should matter or not -- we don't want to weigh some
locales over others -- but I found it interesting.

Regards,
Jeff Davis

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-03-23 20:35:46 Re: Progress report of CREATE INDEX for nested partitioned tables
Previous Message Robert Haas 2023-03-23 20:11:38 Re: refactoring basebackup.c