Re: BUG #17914: walsenders taking up all memory

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(dot)kapila16(at)gmail(dot)com> wrote:

> On Tue, May 2, 2023 at 2:26 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.
> >
>
> 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.
>