| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Todd A(dot) Cook" <tcook(at)blackducksoftware(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14932: SELECT DISTINCT val FROM table gets stuck in an infinite loop |
| Date: | 2017-12-06 17:19:23 |
| Message-ID: | 20171206171923.dg7phzfh7nb4lou3@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2017-12-06 12:14:24 -0500, Tom Lane wrote:
> Checking out hashint8() on random data shows no such obvious fault.
> You've apparently got a data set that exposes a weakness in hashint8,
> but it's not very clear what that is.
It's intentionally designed to cause problems afaict:
> In any case, the hashtable code needs to not fall over in the
> presence of a lot of collisions, regardless of the exact reason
> for there being a lot.
Yes, we need to be more resilient about it. Working on a patch.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Todd A. Cook | 2017-12-06 19:04:56 | Re: BUG #14932: SELECT DISTINCT val FROM table gets stuck in an infinite loop |
| Previous Message | Tom Lane | 2017-12-06 17:14:24 | Re: BUG #14932: SELECT DISTINCT val FROM table gets stuck in an infinite loop |