Re: Time to increase hash_mem_multiplier default?

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Time to increase hash_mem_multiplier default?
Date: 2022-02-17 02:42:45
Message-ID: CAH2-Wzkwn2pVbThrgfWeH6_TC5pA80mZ1LjVi_Q65bb9-o=vgw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Feb 15, 2022 at 8:17 AM Justin Pryzby <pryzby(at)telsasoft(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2022-02-17 02:56:26 Re: do only critical work during single-user vacuum?
Previous Message Kasahara Tatsuhito 2022-02-17 02:26:13 Re: Small and unaffected typo in pg_logical_slot_get_changes_guts()