|From:||Andres Freund <andres(at)anarazel(dot)de>|
|To:||pgsql-hackers(at)lists(dot)postgresql(dot)org,Jeff Davis <pgsql(at)j-davis(dot)com>,pgsql-hackers(at)postgresql(dot)org|
|Subject:||Re: hashagg slowdown due to spill changes|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On June 10, 2020 6:15:39 PM PDT, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
>On Fri, 2020-06-05 at 21:11 -0700, Andres Freund wrote:
>> While preparing my pgcon talk I noticed that our hash-agg performance
>> degraded noticeably. Looks to me like it's due to the spilling-
>Attached a proposed fix. (Might require some minor cleanup).
>The only awkward part is that LookupTupleHashEntry() needs a new out
>parameter to pass the hash value back to the caller. Ordinarily, the
>caller can get that from the returned entry, but if isnew==NULL, then
>the function might return NULL (and the caller wouldn't have an entry
>from which to read the hash value).
Did you run any performance tests?
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|Next Message||Tom Lane||2020-06-11 18:06:06||Definitional issue: stddev_pop (and related) for 1 input|
|Previous Message||Hamid Akhtar||2020-06-11 17:40:38||Re: WIP/PoC for parallel backup|