Re: BUG #17914: walsenders taking up all memory
От | Amit Kapila |
---|---|
Тема | Re: BUG #17914: walsenders taking up all memory |
Дата | |
Msg-id | CAA4eK1JiOt3d8ugDCXmeseVn=Ead5USAP2_Zvi9Q3xG6H-39tg@mail.gmail.com обсуждение исходный текст |
Ответ на | BUG #17914: walsenders taking up all memory (PG Bug reporting form <noreply@postgresql.org>) |
Ответы |
Re: BUG #17914: walsenders taking up all memory
|
Список | pgsql-bugs |
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 по дате отправления: