From: | Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, Daniel Verite <daniel(at)manitou-mail(dot)org>, Joe Conway <mail(at)joeconway(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Inconsistent results with libc sorting on Windows |
Date: | 2023-06-19 07:42:04 |
Message-ID: | CAC+AXB3apkHcfWpjeX8pD1SdrFAzUmue5HwPivYaA+fbmsYOGg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jun 15, 2023 at 1:57 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
>
> Given that the documented behaviour is that ".. the sort key produces
> the same order as when the source string is used in CompareString or
> CompareStringEx"[1], this seems like a reportable bug, unless perhaps
> your test program is hiding an error with that default case you have.
>
> [1]
> https://learn.microsoft.com/en-us/windows/win32/intl/handling-sorting-in-your-applications
Ok, let's see where the report goes:
Regards,
Juan José Santamaría Flecha
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Smith | 2023-06-19 08:29:17 | Re: Initial Schema Sync for Logical Replication |
Previous Message | Michael Paquier | 2023-06-19 07:27:27 | Re: [BUG] recovery of prepared transactions during promotion can fail |