On Tue, Feb 15, 2022 at 8:17 AM Justin Pryzby <pryzby@telsasoft.com> wrote:
> The only reason not to is that a single-node hash-aggregate plan will now use
> 2x work_mem. Which won't make sense to someone who doesn't deal with
> complicated plans (and who doesn't know that work_mem is per-node and can be
> used multiplicitively).
Hearing no objections, I pushed a commit to increase the default to 2.0.
Thanks
--
Peter Geoghegan