From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Refactor to introduce pg_strcoll(). |
Date: | 2022-10-06 23:15:19 |
Message-ID: | 99aa79cceefd1fe84fda23510494b8fbb7ad1e70.camel@j-davis.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Refactors to isolate strcoll, wcscoll, and ucol_strcoll into
pg_locale.c which seems like a better place. Most of the buffer
manipulation and equality optimizations are still left in varlena.c.
Patch attached.
I'm not able to easily test on windows, but it should be close to
correct as I just moved some code around.
Is there a good way to look for regressions (perf or correctness) when
making changes in this area, especially on windows and/or with strange
collation rules? What I did doesn't look like a problem, but there's
always a chance of a regression.
--
Jeff Davis
PostgreSQL Contributor Team - AWS
Attachment | Content-Type | Size |
---|---|---|
0001-Refactor-introduce-pg_strcoll.patch | text/x-patch | 11.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-10-06 23:35:27 | Re: Reducing the chunk header sizes on all memory context types |
Previous Message | Tom Lane | 2022-10-06 23:10:33 | Re: Reducing the chunk header sizes on all memory context types |