From: | Patrick van Dijk <patrick(dot)van(dot)dijk(at)gmail(dot)com> |
---|---|
To: | patrick(dot)van(dot)dijk(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #18523: String compare not consistent |
Date: | 2024-06-26 09:44:54 |
Message-ID: | CAEf=80peQ8Ec8yaR-UpoPHsX8ds31ncX1MX4jYTD7ENLSdsF2A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Windows: PostgreSQL 16.2, compiled by Visual C++ build 1937, 64-bit
On Azure: PostgreSQL 16.3 on x86_64-pc-linux-gnu, compiled by gcc (GCC)
11.2.0, 64-bit
On Wed, Jun 26, 2024 at 11:44 AM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 18523
> Logged by: Patrick van Dijk
> Email address: patrick(dot)van(dot)dijk(at)gmail(dot)com
> PostgreSQL version: 16.3
> Operating system: Windows vs Linux/Azure
> Description:
>
> When I try the following on a Azure/Linux version of PostgreSQL i see some
> strange results that are not correct.
> On Windows the behavior is correct.
>
> select '|' < '0'; -- true, true, this is correct
> select '|1' < '01'; -- false, true, Azure/Linux is wrong
> select '||' < '0|'; -- true, true, this is correct
> select '||1' < '0|1'; -- false, true, Azure/Linux is wrong
>
> When the first character compares <, then no matter what follows, it should
> be <...
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Patrick van Dijk | 2024-06-26 10:11:50 | Re: BUG #18523: String compare not consistent |
Previous Message | PG Bug reporting form | 2024-06-26 09:43:42 | BUG #18523: String compare not consistent |