Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #17914: walsenders taking up all memory - Mailing list pgsql-bugs

From Stan S
Subject Re: BUG #17914: walsenders taking up all memory
Date
Msg-id CAHcftXob2_9QNxN0uDRyAZbTa_HS8tkZ=V6rQ=UPKtf2X=9k5Q@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17914: walsenders taking up all memory  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-bugs
Tree view
Hi Amit,

Yes, I believe it's a similar issue. However, we can't patch it up the same way Alex did because we use Postgres via AWS RDS.

On Wed, May 3, 2023 at 11:36 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
On Tue, May 2, 2023 at 2:26 AM PG Bug reporting form
<noreply@postgresql.org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference:      17914
> Logged by:          Stan S
> Email address:      stashukny@gmail.com
> PostgreSQL version: 14.3
> Operating system:   AWS RDS - (Red Hat 7.3.1-12), 64-bit
> Description:
>
> Seeing the same issue as reported here:
> https://www.postgresql.org/message-id/CAMnUB3oYugXCBLSkih%2BqNsWQPciEwos6g_AMbnz_peNoxfHwyw%40mail.gmail.com
>
> In our case, logical_decoding_work_mem is set to 64 MB, yet walsenders can
> each take up 30 GB of memory, crashing our database.
>

I think we have previously also seen a similar complaint. Can you
please once check the analysis related to memory context in email [1]
and see if this is a similar problem?

[1] - https://www.postgresql.org/message-id/CAMnUB3pwknqoe5s-bGuRD8nX1bWkZRbFF=jWNLTWbm_etFigkA@mail.gmail.com

--
With Regards,
Amit Kapila.

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Bug：Create a table with 1600 fields (reaching the upper limit), then drop several fields and create new ones, but the addition failed.
Next
From: Alexander Lakhin
Date:
Subject: Re: BUG #17920: Incorrect memory access in array_position(s) is detected (or not)