Re: Order changes in PG16 since ICU introduction

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Sandro Santilli <strk(at)kbt(dot)io>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Regina Obe <lr(at)pcorp(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Order changes in PG16 since ICU introduction
Date: 2023-06-07 15:03:26
Message-ID: d737e3b0-1a02-c0b7-4a51-8b16eacaba24@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 22.05.23 19:35, Jeff Davis wrote:
> On Thu, 2023-05-11 at 13:07 +0200, Peter Eisentraut wrote:
>> Here is my proposed patch for this.
>
> The commit message makes it sound like lc_collate/ctype are completely
> obsolete, and I don't think that's quite right: they still represent
> the server environment, which does still matter in some cases.
>
> I'd just say that they are too confusing (likely to be misused), and
> becoming obsolete (or less relevant), or something along those lines.
>
> Otherwise, this is fine with me. I didn't do a detailed review because
> it's just mechanical.

I have committed this with some tuning of the commit message.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message 謝東霖 2023-06-07 15:05:19 Re: Improve join_search_one_level readibilty (one line change)
Previous Message Tristan Partin 2023-06-07 14:31:10 Fix last unitialized memory warning