On Fri, Jul 24, 2020 at 4:51 PM Andres Freund <and...@anarazel.de> wrote: > This is still not resolved. We're right now slower than 12. It's > effectively not possible to do performance comparisons right now. This > was nearly two months ago.
I have added a new open item for this separate LookupTupleHashEntryHash()/lookup_hash_entry() pipeline-stall issue. (For the record I mistakenly believed that commit 23023022 resolved all of the concerns raised on this thread, which is why I closed out the open item associated with this thread. Evidently work remains to fix a remaining regression that affects simple in-memory hash aggregation, though.) -- Peter Geoghegan
