pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: JOIGNY Michael @Neteven <mjoigny@neteven.com>
To: pgsql-admin@postgresql.org
Subject: Cannot allocate memory
Date: Fri, 18 Sep 2020 12:03:50 +0200
Message-ID: <e839bc32-d827-c840-88ae-52acc3a359eb@neteven.com> (raw)

Hi Community,

I'm asking for your lights because i'm having memory problems with postgres.

Examples of logs :

/FATAL: could not fork new process for connection: Cannot allocate 
memory could not fork new process for connection: Cannot allocate memory
out of memory  DETAIL:  Failed on request of size 32800 in memory 
context "HashBatchContext".
out of memory DETAIL Failed on request of size 288 in memory context 
"CacheMemoryContext".
/

We use postgresql (primary/standby) with pgbouncer as a pooler, and 
repmgr as replication manager.

We have ~ 2000 connections at the same time with ~ 20/30 are active. (we 
need to set a high number of connexion on postgres, because our app uses 
a lot of different users, and each user on each app server needs 
multiple and constant connexions).

Here is my configuration :

_system : _

Debian : 9.13
Memory : 380 Go
Postgres : 12.4-1.pgdg90+1
Pgbouncer : 1.14
kernel.shmmax = 202591600640
kernel.shmall = 49460840

_postgres :
_

dynamic_shared_memory_type = posix    # the default is the first option
max_connections = 2600            # (change requires restart)
work_mem = 96MB                # min 64kB
maintenance_work_mem = 8GB        # min 1MB
shared_buffers = 64GB            # min 128kB
temp_buffers = 32MB            # min 800kB
wal_buffers = 16MB            # min 32kB, -1 sets based on shared_buffers
effective_cache_size = 270GB

pgbouncer :

max_client_conn = 6000
default_pool_size = 2590
reserve_pool_size = 5
pool_mode = session

Do you think that our parameters are not correct compared to our 
configuration? Do you have an idea ?

Best regards.

Michael.

view thread (7+ messages)  latest in thread

Message-ID: <e839bc32-d827-c840-88ae-52acc3a359eb@neteven.com>
Permalink:  ../e839bc32-d827-c840-88ae-52acc3a359eb@neteven.com/
Also on:    postgresql.org/message-id/e839bc32-d827-c840-88ae-52acc3a359eb@neteven.com

 · 

reply

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: mjoigny@neteven.com
  Subject: Re: Cannot allocate memory
  In-Reply-To: <e839bc32-d827-c840-88ae-52acc3a359eb@neteven.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