Disk-based hash aggregate's cost model - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Disk-based hash aggregate's cost model
Date
Msg-id CAH2-Wzk1-JiW2heHg8LqJzV5Q4VtOBj7QDXTESd_o0Vzo+_Etw@mail.gmail.com
Whole thread Raw
Responses Re: Disk-based hash aggregate's cost model  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
We have a Postgres 13 open item for Disk-based hash aggregate, which
is the only non-trivial open item. There is a general concern about
how often we get disk-based hash aggregation when work_mem is
particularly low, and recursion seems unavoidable. This is generally
thought to be a problem in the costing.

Tomas Vondra did some testing of the patch which led to discussion of
this on the hash agg GUC megathread, here:

https://www.postgresql.org/message-id/20200724012248.y77rpqc73agrsvb3@development

I am starting this new thread to deal with the open item.

Any progress on this, Jeff? Please correct or expand on my summary of
the open item if I got something wrong.

Thanks
-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Ranier Vilela
Date:
Subject: [PATCH] Explicit null dereferenced (src/backend/access/heap/heaptoast.c)
Next
From: Stephen Frost
Date:
Subject: New default role- 'pg_read_all_data'