From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: melody_xiaodi@sina.com
Subject: BUG #18450: The memory usage of the postgresql12.6 walsender process is abnormally high.
Date: Sat, 27 Apr 2024 06:02:26 +0000
Message-ID: <18450-3c557c332cef9d6d@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 18450
Logged by: Melody Liu
Email address: melody_xiaodi@sina.com
PostgreSQL version: 12.6
Operating system: CentOS Linux release 7.9.2009
Description:
In my PostgreSQL 12.6 database, the memory usage of the walsender process
continues to rise, even during periods of low business activity. According
to current monitoring results, the walsender process can occupy up to 61G of
memory and is still increasing. Only after restarting the walsender process
can the server memory be released.
Configuration description of postgresql12.6: The OS has set hugepages with a
maximum limit of 165G, and shared_buffers is set to 150G. My server
configuration is as follows: CPU: 64core, MEM: 256G.
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-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, melody_xiaodi@sina.com
Subject: Re: BUG #18450: The memory usage of the postgresql12.6 walsender process is abnormally high.
In-Reply-To: <18450-3c557c332cef9d6d@postgresql.org>
* 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