Re: Default setting for enable_hashagg_disk - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Default setting for enable_hashagg_disk
Date
Msg-id CAKFQuwa=pw2Auipt5-Gwf8itObZDF2krj9dNiypFca=7g8uebA@mail.gmail.com
Whole thread Raw
In response to Re: Default setting for enable_hashagg_disk  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: Default setting for enable_hashagg_disk  (Peter Geoghegan <pg@bowt.ie>)
Re: Default setting for enable_hashagg_disk  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Jul 13, 2020 at 11:50 AM Peter Geoghegan <pg@bowt.ie> wrote:

Primarily in favor of escape hatch:

Jeff,
DavidR,
Pavel,
Andres,
Robert ??,
Amit ??


To be clear, by "escape hatch" you mean "add a GUC that instructs the PostgreSQL executor to ignore hash_mem when deciding whether to spill the contents of the hash table to disk - IOW to never spill the contents of a hash table to disk"?  If so that seems separate from whether to add a hash_mem GUC to provide finer grained control - people may well want both.

Primarily in favor of hash_mem/hash_mem_multiplier:

PeterG,
Tom,
Alvaro,
Tomas,
Justin,
DavidG,
Jonathan Katz


I would prefer DavidJ as an abbreviation - my middle initial can be dropped when referring to me.

David J.

pgsql-hackers by date:

Previous
From: Alexey Kondratov
Date:
Subject: Partitioning and postgres_fdw optimisations for multi-tenancy
Next
From: Andrew Dunstan
Date:
Subject: Re: pg_dump bug for extension owned tables