Re: Order changes in PG16 since ICU introduction

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Jeff Davis <pgsql(at)j-davis(dot)com>, Daniel Verite <daniel(at)manitou-mail(dot)org>
Cc: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Order changes in PG16 since ICU introduction
Date: 2023-06-07 21:59:59
Message-ID: 5b6a38b4-56e3-4f4b-966a-ac8c80ae4f66@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 05.06.23 19:54, Jeff Davis wrote:
>
> New patch series attached. I plan to commit 0001 and 0002 soon, unless
> there are objections.
>
> 0001 causes the "C" and "POSIX" locales to be treated with
> memcmp/pg_ascii semantics in ICU, just like in libc. We also considered
> a new "none" provider, but it's more invasive, and we can always
> reconsider that in the v17 cycle.
>
> 0002 introduces an upgrade check for users who have explicitly
> requested provider=icu and iculocale=C on older versions, and rejects
> upgrading from v15 in that case to avoid index corruption. Having such
> a collation is almost certainly a mistake by the user, because the
> collator would not give the expected memcmp semantics.

I'm dubious about these two.

0003 seems like the correct direction. In createdb.c, the change you
add makes sense, but you should also remove the existing use of the
locale variable:

- if (locale)
- {
- if (!lc_ctype)
- lc_ctype = locale;
- if (!lc_collate)
- lc_collate = locale;
- }
-

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2023-06-07 22:04:16 Re: v16 fails to build w/ Visual Studio 2015
Previous Message Andres Freund 2023-06-07 21:58:09 Re: Let's make PostgreSQL multi-threaded