From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: mguissine@gmail.com
Subject: BUG #17974: Walsenders memory usage suddenly spike to 80G+ causing OOM and server reboot
Date: Wed, 14 Jun 2023 00:05:32 +0000
Message-ID: <17974-f8c9d353a62f414d@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 17974
Logged by: Michael Guissine
Email address: mguissine@gmail.com
PostgreSQL version: 14.8
Operating system: AWS RDS
Description:
We are running relatively large and busy Postgres database on RDS and using
logical replication extensively. We currently have 7 walsenders and while we
often see replication falls behind due to high transactional volume, we've
never experienced memory issues in 14.6 and below. After recent upgrade to
14.8, we already had several incidents where walsender processes RES memory
would suddenly increase to over 80GB each causing freeable memory on the
instance to go down to zero. Interesting that even after Instance reboot,
the memory used by walsender processes won't get released until we restart
the replication and drop the logical slots. The logical_decoding_work_mem
was set to 512MB in time of the last incident but we recently lowered it to
128MB.
Any known issues in pg 14.8 that would trigger this behaviour?
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, mguissine@gmail.com
Subject: Re: BUG #17974: Walsenders memory usage suddenly spike to 80G+ causing OOM and server reboot
In-Reply-To: <17974-f8c9d353a62f414d@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