From: | Alfonso Vicente <alfonsovicente(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #17168: Incorrect sorting |
Date: | 2021-08-30 18:16:20 |
Message-ID: | CACf42wbuqpjSrdLeR9SXbXrv4Rp46vVOa0L8JObP8X1SU-PBwg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
You're right, I was incorrectly working with en_US.UTF-8 lc_collate because
of a cloning issue
Regards,
Alfonso Vicente
On Mon, Aug 30, 2021 at 3:09 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Monday, August 30, 2021, PG Bug reporting form <noreply(at)postgresql(dot)org>
> wrote:
>
>> The following bug has been logged on the website:
>>
>> Bug reference: 17168
>> Logged by: Alfonso Vicente
>> Email address: alfonsovicente(at)gmail(dot)com
>> PostgreSQL version: 13.2
>> Operating system: Red Hat Enterprise Linux 8
>> Description:
>>
>> This is a minimal example to reproduce the error, the "ara" tuple is
>> incorrectly sorted between "a r" and "a s"
>>
>
> By what authority are you claiming that the correct order is not this
> (i.e., what claim is being violated, and thus is buggy?). And what are the
> sort-related settings that are in effect?
>
> David J.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-08-31 02:39:35 | Re: BUG #17161: Assert failed on opening a relation that exists in two schemas via the LANGUAGE SQL function |
Previous Message | David G. Johnston | 2021-08-30 18:09:08 | Re: BUG #17168: Incorrect sorting |