Re: Default setting for enable_hashagg_disk (hash_mem) - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Default setting for enable_hashagg_disk (hash_mem)
Date
Msg-id 20200707201821.GA24503@alvherre.pgsql
Whole thread Raw
In response to Re: Default setting for enable_hashagg_disk (hash_mem)  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Default setting for enable_hashagg_disk (hash_mem)  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-hackers
On 2020-Jul-07, Amit Kapila wrote:

> I don't think this is true.  We seem to have introduced three new guc
> variables in a 9.3.3 minor release.

Yeah, backporting GUCs is not a big deal.  Sure, the GUC won't appear in
postgresql.conf files generated by initdb prior to the release that
introduces it.  But users that need it can just edit their .confs and
add the appropriate line, or just do ALTER SYSTEM after the minor
upgrade.  For people that don't need it, it would have a reasonable
default (probably work_mem, so that behavior doesn't change on the minor
upgrade).

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



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Default setting for enable_hashagg_disk (hash_mem)
Next
From: Peter Geoghegan
Date:
Subject: Re: Default setting for enable_hashagg_disk (hash_mem)