From: Michael Paquier <michael@paquier.xyz>
To: Michael Guissine <mguissine@gmail.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17974: Walsenders memory usage suddenly spike to 80G+ causing OOM and server reboot
Date: Thu, 15 Jun 2023 10:02:39 +0900
Message-ID: <ZIpjL+j9OwnOuuYX@paquier.xyz> (raw)
In-Reply-To: <CACxDrAkywDL2y5DyLL9fxDzPhKUFBaCZ9D2gkP7OzQsd7GQXng@mail.gmail.com>
References: <17974-f8c9d353a62f414d@postgresql.org>
<ZIkWlJNVSN1hKnYw@paquier.xyz>
<20230614221503.ux62wn25bhydnzjm@awork3.anarazel.de>
<CACxDrAkywDL2y5DyLL9fxDzPhKUFBaCZ9D2gkP7OzQsd7GQXng@mail.gmail.com>
On Wed, Jun 14, 2023 at 08:04:53PM -0400, Michael Guissine wrote:
> On Wed, Jun 14, 2023 at 6:15 PM Andres Freund <andres@anarazel.de> wrote:
>>>> Any known issues in pg 14.8 that would trigger this behaviour?
>>>
>>> Yes, there are known issues with memory handling in logical
>>> replication setups. See for example this thread:
>>>
>>> https://www.postgresql.org/message-id/CAMnUB3oYugXCBLSkih+qNsWQPciEwos6g_AMbnz_peNoxfHwyw@mail.gmail...
>>
>> Why would 14.8 have made that problem worse?
Hmm? I don't necessarily imply that 14.8 made it worse, but that
there are known issues in this area as the other thread mention (which
is mainly about v15, actually, where the situation could be a bit
better).
> This is an assumption obviously, based on the fact that we have been
> running this database for several years already and haven't seen similar
> memory issues until the recent upgrade to 14.8.
Was that all the time with 14 as base? What are the minor versions
you used in the past? Perhaps there is a correlation here that could
help a bit. There have been a few things in this area lately, like
9f2cc1a, 4fbe609, 68dcce2, fd270b7 or 8b9cbd4 (this one made the
decoding cheaper), so it could be possible that a defect has been
introduced. Being able to know the contexts where the memory is
piling up would help a lot, for sure.
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
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: michael@paquier.xyz, mguissine@gmail.com, andres@anarazel.de, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17974: Walsenders memory usage suddenly spike to 80G+ causing OOM and server reboot
In-Reply-To: <ZIpjL+j9OwnOuuYX@paquier.xyz>
* 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