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

From Peter Geoghegan
Subject Re: Default setting for enable_hashagg_disk
Date
Msg-id CAH2-WznKb9aT2nbUVJnF1qCqYJ+HAj2C2UHe5B_DJqANoAOCmg@mail.gmail.com
Whole thread Raw
In response to Re: Default setting for enable_hashagg_disk  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
List pgsql-hackers
On Sun, Jul 26, 2020 at 11:34 AM Tomas Vondra
<tomas.vondra@2ndquadrant.com> wrote:
> That's 1.6GB, if I read it right. Which is more than 200MB ;-)

Sigh. That solves that "mystery": the behavior that my sorted vs
random example exhibited is a known limitation in hash aggs that spill
(and an acceptable one). The memory usage is reported on accurately by
EXPLAIN ANALYZE.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: hashagg slowdown due to spill changes
Next
From: Dave Page
Date:
Subject: Re: Display individual query in pg_stat_activity