From: | "Todd A(dot) Cook" <tcook(at)blackducksoftware(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #14932: SELECT DISTINCT val FROM table gets stuck in an infinite loop |
Date: | 2017-11-28 14:49:34 |
Message-ID: | 50475a99-d9fc-66b2-6c7f-b4f81e9567d6@blackducksoftware.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 11/27/17 17:10, Andres Freund wrote:
> Hi,
>
> On 2017-11-27 15:59:37 -0500, Todd A. Cook wrote:
>> COPY reproducer (val) FROM stdin;
>> 2976219712004784288
>> -6429122065899879392
>> -7471109962990387136
>> -7471109962990387136
>> -2895470491222113184
>> -4083509061952565472
>> 1019481548263425664
>> 4639248884787347648
>> -6999443831165647744
>> -4199917803455020480
>> -4110530183001439680
>
> How are these values generated? They awfully look like hash values
> (~same lenght, full numerical range)...
They are biased hashes. FWIW, the reproducer data is from one column of a
three-column primary key.
-- todd
From | Date | Subject | |
---|---|---|---|
Next Message | Todd A. Cook | 2017-11-28 14:55:13 | Re: BUG #14932: SELECT DISTINCT val FROM table gets stuck in an infinite loop |
Previous Message | Tomas Vondra | 2017-11-28 13:08:10 | Re: BUG #14932: SELECT DISTINCT val FROM table gets stuck in an infinite loop |