| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Custom Glibc collation version strings under LOCPATH |
| Date: | 2025-06-05 01:00:26 |
| Message-ID: | 21dca872-1270-4c17-9622-b071c9a1c265@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/4/25 19:35, Thomas Munro wrote:
> On Thu, Jun 5, 2025 at 3:44 AM Joe Conway <mail(at)joeconway(dot)com> wrote:
>> If you go from anything pre-glibc-2.21 to post-glibc-2.21 I think you
>> will find that even with the same data files you get a different sort.
>> The same patch that caused the performance regression [1] (still present
>> in up to date glibc) also cause changes in sort order via C code alone.
> Finding more cases probably involves running something a little like
> Jeremy's torture tests across a huge gallery of versions and
> combinations of cross-version recompiled definitions. Or something
> like that...
Sounds like great fun!
;-)
--
Joe Conway
PostgreSQL Contributors Team
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2025-06-05 01:00:42 | Re: Improve explicit cursor handling in pg_stat_statements |
| Previous Message | Michael Paquier | 2025-06-05 00:52:40 | Re: Encapsulate io_uring process count calculation |