From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
---|---|
To: | David Raymond <David(dot)Raymond(at)tomtom(dot)com> |
Cc: | "pgsql-bugs\(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #16031: Group by returns duplicate groups |
Date: | 2019-10-01 19:26:56 |
Message-ID: | 87h84sl1b5.fsf@news-spur.riddles.org.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
>>>>> "David" == David Raymond <David(dot)Raymond(at)tomtom(dot)com> writes:
David> I checked for other places where there was weirdness going on
David> and there are more.
You could try something like,
select name, lname
from (select name, lag(name) over (order by name) as lname
from big_table) s
where name < lname;
That should show all cases where the sort order was inconsistent with
the < operator (which obviously should never happen).
However, there's not much more I can do to help with this, since I don't
use Windows myself and have no useful access to any Windows system. You
might try and cut down the data to the smallest set that shows
inconsistencies using the above; particularly relevant is whether the
problem only shows up for external merge sorts or whether it happens for
in-memory sorts too.
--
Andrew (irc:RhodiumToad)
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2019-10-02 12:04:42 | BUG #16033: segmentation fault when runing update |
Previous Message | David Raymond | 2019-10-01 18:34:38 | RE: BUG #16031: Group by returns duplicate groups |