From: Mladen Gogala <gogala.mladen@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: PostgreSQL Out of Memory
Date: Mon, 5 Sep 2022 11:25:55 -0400
Message-ID: <eab6a451-f181-c179-b423-6e63753aeddb@gmail.com> (raw)
In-Reply-To: <CAGHjuaYK33cGgHYUm1ObnxPJ2a8TSnSwcVDXGb4Fk1qfP12gGA@mail.gmail.com>
References: <CAGHjuaYK33cGgHYUm1ObnxPJ2a8TSnSwcVDXGb4Fk1qfP12gGA@mail.gmail.com>
On 9/5/22 07:54, liam saffioti wrote:
> Hi Teams,
>
> FATAL: terminating background worker "parallel worker" due to
> administrator command
> FATAL: terminating background worker "parallel worker" due to
> administrator command
> FATAL: terminating background worker "parallel worker" due to
> administrator command
> FATAL: out of memory
> FATAL: out of memory
> ...
You are allowing over-committing memory, which in turn activates OOMK
(Out of Memory Killer) when the memory runs out. You have to restrict
the number of connections or parameters like work_mem and
hash_mem_multiplier. There is also a good article on Squishy Data:
https://www.crunchydata.com/blog/deep-postgresql-thoughts-the-linux-assassin
Basically, you should start with vm.overcommit_memory = 2
--
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
https://dbwhisperer.wordpress.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: gogala.mladen@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: PostgreSQL Out of Memory
In-Reply-To: <eab6a451-f181-c179-b423-6e63753aeddb@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox