pgsql: Fix HashAgg regression from choosing too many initial buckets.

From: Jeff Davis <jdavis(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix HashAgg regression from choosing too many initial buckets.
Date: 2020-06-09 04:07:27
Message-ID: E1jiVXr-0004S2-Jm@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix HashAgg regression from choosing too many initial buckets.

Diagnosis by Andres.

Reported-by: Pavel Stehule
Discussion: https://postgr.es/m/CAFj8pRDLVakD5Aagt3yZeEQeTeEWaS3YE5h8XC3Q3qJ6TYkc2Q%40mail.gmail.com
Backpatch-through: 13

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/1b2c29469a58cd9086bd86e20c708eb437564a80

Modified Files
--------------
src/backend/executor/nodeAgg.c | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Jeff Davis 2020-06-09 04:12:05 pgsql: Fix HashAgg regression from choosing too many initial buckets.
Previous Message Andres Freund 2020-06-09 03:25:01 pgsql: Avoid need for valgrind suppressions for pg_atomic_init_u64 on s