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

From David Rowley
Subject Re: Default setting for enable_hashagg_disk
Date
Msg-id CAApHDvoOOsxTxb6xjdTBR0ZxXB9tQcqwXgY2tfF6QEKM5LG47Q@mail.gmail.com
Whole thread Raw
In response to Re: Default setting for enable_hashagg_disk  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: Default setting for enable_hashagg_disk  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-hackers
On Sat, 11 Jul 2020 at 13:36, David G. Johnston
<david.g.johnston@gmail.com> wrote:
> If we add a setting that defaults to work_mem then the benefit is severely reduced.  You still have to modify
individualqueries, but the change can simply be more targeted than changing work_mem alone.
 

I think the idea is that this is an escape hatch to allow users to get
something closer to what PG12 did, but only if they really need it.  I
can't quite understand why we need to leave the escape hatch open and
push them halfway through it.  I find escape hatches are best left
closed until you really have no choice but to use them.

David



pgsql-hackers by date:

Previous
From: Soumyadeep Chakraborty
Date:
Subject: Re: Does TupleQueueReaderNext() really need to copy its result?
Next
From: "David G. Johnston"
Date:
Subject: Re: Default setting for enable_hashagg_disk