| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | melody_xiaodi(at)sina(dot)com |
| Subject: | BUG #18450: The memory usage of the postgresql12.6 walsender process is abnormally high. |
| Date: | 2024-04-27 06:02:26 |
| Message-ID: | 18450-3c557c332cef9d6d@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 18450
Logged by: Melody Liu
Email address: melody_xiaodi(at)sina(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2024-04-27 14:37:56 | Re: BUG #17257: (auto)vacuum hangs within lazy_scan_prune() |
| Previous Message | PG Bug reporting form | 2024-04-27 04:00:01 | BUG #18449: Altering column type fails when an SQL routine depends on the column |