Re: Enforce work_mem per worker

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Arne Roland <A(dot)Roland(at)index(dot)de>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Enforce work_mem per worker
Date: 2021-11-29 15:10:59
Message-ID: 20211129151059.GM17618@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 29, 2021 at 02:01:35PM +0000, Arne Roland wrote:
> But my main goal is something else. I can't explain my clients, why a chanced statistics due to autovacuum suddenly leads to oom. They would be right to question postgres qualification for any serious production system.

What version postgres was that on ?

I realize it doesn't address your question, but since PG13, HashAggregate
respects work_mem. Depending on the details of the query plan, that's arguably
a bigger problem than the absence of a global work_mem. At least that one is
resolved.

--
Justin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2021-11-29 15:15:35 Re: Lots of memory allocated when reassigning Large Objects
Previous Message Euler Taveira 2021-11-29 15:10:09 Re: row filtering for logical replication