Re: BUG #17068: Incorrect ordering of a particular row.

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: ganeshmmahesh(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17068: Incorrect ordering of a particular row.
Date: 2021-06-22 13:32:37
Message-ID: CAApHDvps-nsv4nwr-64OFp9APNxbB++=LvhP+gN+JWJ3wXJYiQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, 23 Jun 2021 at 01:06, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> It seems a bit fishy that the only 4s that appear here are being
> compared to 4. How does qsort figure out that 5 > 4 or 4 < 5?

Even if I change the < 7 qsort optimization in sort_template.h
(working in master here) to be < 7000 so we bubble sort everything
here, I still don't see 4 being compared to any other value. Something
else must be going on.

David

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2021-06-22 13:42:18 Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
Previous Message Thomas Munro 2021-06-22 13:25:30 Re: BUG #17068: Incorrect ordering of a particular row.