Re: BUG #17914: walsenders taking up all memory

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: stashukny(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17914: walsenders taking up all memory
Date: 2023-05-03 07:29:33
Message-ID: CAD21AoCaB8soqN9mUg8wjLfoAHLdC4PLmAnqcvpp07YJuTPB7A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On Tue, May 2, 2023 at 5:56 AM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference: 17914
> Logged by: Stan S
> Email address: stashukny(at)gmail(dot)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.

Thank you for reporting this issue. I have two questions:

* Did you use streaming = off/on on the subscriber?
* How did you confirm the walsender used 30GB of memory?

Regards,

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2023-05-03 10:01:21 BUG #17917: to_tsquery syntax error
Previous Message PG Bug reporting form 2023-05-03 05:19:07 BUG #17916: Expression IN list translates to unqualified operator