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 CAApHDvpQ91e2ty1_C8o0PsEyPTA+WGZZcC=R0H9CPE3s2HW2hg@mail.gmail.com
Whole thread Raw
In response to Re: Default setting for enable_hashagg_disk  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Default setting for enable_hashagg_disk  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On Mon, 13 Jul 2020 at 23:51, Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
> I have an anecdote that might be related to this discussion.
>
> I was running an unrelated benchmark suite.  With PostgreSQL 12, one
> query ran out of memory.  With PostgreSQL 13, the same query instead ran
> out of disk space.  I bisected this to the introduction of disk-based
> hash aggregation.  Of course, the very point of that feature is to
> eliminate the out of memory and make use of disk space instead.  But
> running out of disk space is likely to be a worse experience than
> running out of memory.  Also, while it's relatively easy to limit memory
> use both in PostgreSQL and in the kernel, it is difficult or impossible
> to limit disk space use in a similar way.

Isn't that what temp_file_limit is for?

David



pgsql-hackers by date:

Previous
From: wenjing zeng
Date:
Subject: Re: [Proposal] Global temporary tables
Next
From: Michael Paquier
Date:
Subject: Re: Don't choke on files that are removed while pg_rewind runs.