Re: max_memory_per_backend GUC to limit backend's memory usage

From: Andres Freund <andres(at)anarazel(dot)de>
To: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: max_memory_per_backend GUC to limit backend's memory usage
Date: 2018-03-23 16:06:53
Message-ID: 20180323160653.xmwf2ci3lwzlru6g@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2018-03-23 15:58:55 +0000, Vladimir Sitnikov wrote:
> I've got a problem with PostgreSQL 9.6.5: backend gets killed by OOM
> killer, and it shuts the DB down.
> Of course, the OOM case is to be investigated (MemoryContextStatsDetail,
> etc), however I wonder if DB can be more robust.

Configuring overcommit_memory to not overcommit should do the trick.

Greetings,

Andres Freund

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Konstantin Knizhnik 2018-03-23 16:08:59 Re: [HACKERS] Surjective functional indexes
Previous Message Vladimir Sitnikov 2018-03-23 15:58:55 max_memory_per_backend GUC to limit backend's memory usage