Re: ICU for global collation

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Daniel Verite <daniel(at)manitou-mail(dot)org>
Subject: Re: ICU for global collation
Date: 2022-01-10 03:25:08
Message-ID: 20220110032508.4eyz6m6mpvt622la@jrouhaud
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jan 07, 2022 at 03:25:28PM +0100, Peter Eisentraut wrote:
>
> I tested this a bit. I used the following setup:
>
> create table t1 (a text);
> insert into t1 select md5(generate_series(1, 10000000)::text);
> select count(*) from t1 where a > '';
>
> And then I changed in varstr_cmp():
>
> if (collid != DEFAULT_COLLATION_OID)
> mylocale = pg_newlocale_from_collation(collid);
>
> to just
>
> mylocale = pg_newlocale_from_collation(collid);
>
> I find that the \timing results are indistinguishable. (I used locale
> "en_US.UTF-8" and made sure that that code path is actually hit.)
>
> Does anyone have other insights?

Looking at the git history, you added this comment in 414c5a2ea65.

After a bit a digging in the lists, I found that you introduced it to fix a
reported 13% slowdown in varstr_cmp():
https://www.postgresql.org/message-id/20110129075253.GA18784%40tornado.leadboat.com
https://www.postgresql.org/message-id/1296748408.6442.1.camel%40vanquo.pezone.net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message houzj.fnst@fujitsu.com 2022-01-10 03:31:03 RE: row filtering for logical replication
Previous Message houzj.fnst@fujitsu.com 2022-01-10 03:16:39 RE: row filtering for logical replication