Re: BUG #14932: SELECT DISTINCT val FROM table gets stuck in an infinite loop

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Todd A(dot) Cook" <tcook(at)blackducksoftware(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: 2018-01-29 17:06:31
Message-ID: 20180129170631.kdr2dtu5rodvovhv@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On 2018-01-29 14:41:49 +0100, Tomas Vondra wrote:
> Do you think repeating the performance testing is necessary? Not sure
> when do you plan to push the changes, I may not have time for the tests
> until after FOSDEM.

Hm, it surely wouldn't hurt, but your previous result does give a lot of
confidence - there's not a lot of fundamental difference leaving one
more mitigation that should never reduce hashtable "quality" aside. So
I think going ahead with pushing and then benchmarking if possible, is
reasonable?

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Mauricio Alejandro De León Cárdenas 2018-01-29 17:40:16 Database creation taking too long
Previous Message PG Bug reporting form 2018-01-29 16:48:53 BUG #15036: Un-killable queries Hanging in BgWorkerShutdown