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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, "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 18:29:40
Message-ID: 5614.1517250580@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Andres Freund <andres(at)anarazel(dot)de> writes:
> On January 29, 2018 10:11:38 AM PST, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Since the release wrap is this coming Monday, there's not really time
>> to wait and do something after FOSDEM ...

> I'm not sure what you're arguing for? I have measured the performance impacts, and am happy. That's why I do not want to wait till then. Doing additional benchmarks after commit can't hurt tho...

I'm arguing for not waiting. If Tomas does some more benchmarking and
finds something else we can improve, that's fine, but the stop-growing
patch is already an important fix compared to 10.1.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2018-01-29 18:30:49 Re: BUG #14932: SELECT DISTINCT val FROM table gets stuck in an infinite loop
Previous Message Tom Lane 2018-01-29 18:25:35 Re: BUG #14932: SELECT DISTINCT val FROM table gets stuck in an infinite loop