Re: BUG #17914: walsenders taking up all memory
От | Masahiko Sawada |
---|---|
Тема | Re: BUG #17914: walsenders taking up all memory |
Дата | |
Msg-id | CAD21AoCaB8soqN9mUg8wjLfoAHLdC4PLmAnqcvpp07YJuTPB7A@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 |
Hi, On Tue, May 2, 2023 at 5:56 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. 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
В списке pgsql-bugs по дате отправления: