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

From Alvaro Herrera
Subject Re: Default setting for enable_hashagg_disk
Date
Msg-id 20200625225853.GA11137@alvherre.pgsql
Whole thread Raw
In response to Re: Default setting for enable_hashagg_disk  (Andres Freund <andres@anarazel.de>)
Responses Re: Default setting for enable_hashagg_disk  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On 2020-Jun-25, Andres Freund wrote:

> >My point here is that maybe we don't need to offer a GUC to explicitly
> >turn spilling off; it seems sufficient to let users change work_mem so
> >that spilling will naturally not occur.  Why do we need more?
> 
> That's not really a useful escape hatch, because I'll often lead to
> other nodes using more memory.

Ah -- other nodes in the same query -- you're right, that's not good.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: should libpq also require TLSv1.2 by default?
Next
From: Tomas Vondra
Date:
Subject: Re: Default setting for enable_hashagg_disk