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

From Bruce Momjian
Subject Re: Default setting for enable_hashagg_disk
Date
Msg-id 20200624231517.GA13627@momjian.us
Whole thread Raw
In response to Re: Default setting for enable_hashagg_disk  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
List pgsql-hackers
On Wed, Jun 24, 2020 at 11:02:10PM +0200, Tomas Vondra wrote:
> > Indeed. And then perhaps we could eventually add some reporting /
> > monitoring infrastructure for the cases where plan time and execution
> > time memory estimate/usage widely differs.
> > 
> 
> I wouldn't mind something like that in general - not just for hashagg,
> but for various other nodes.

Well, other than worrying about problems with pre-13 queries, how is
this different from any other spill to disk when we exceed work_mem,
like sorts for merge join.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee




pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Why forbid "INSERT INTO t () VALUES ();"
Next
From: Bruce Momjian
Date:
Subject: Re: Default setting for enable_hashagg_disk