| From: | Amit Kapila <amit(dot)kapila16(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-04 03:36:32 |
| Message-ID: | CAA4eK1JiOt3d8ugDCXmeseVn=Ead5USAP2_Zvi9Q3xG6H-39tg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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?
--
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Guo | 2023-05-04 11:22:24 | Re: Clause accidentally pushed down ( Possible bug in Making Vars outer-join aware) |
| Previous Message | Devrim Gündüz | 2023-05-03 22:23:43 | Re: BUG #17918: Checksum failed while sync repos for a package |