| From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Michael Guissine <mguissine(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17974: Walsenders memory usage suddenly spike to 80G+ causing OOM and server reboot |
| Date: | 2023-06-15 01:20:13 |
| Message-ID: | CAD21AoAm-WZOGXZcwbV6=inn=1EOSDPNizFJBE0xOuM0kmxrqg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Jun 15, 2023 at 10:02 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Wed, Jun 14, 2023 at 08:04:53PM -0400, Michael Guissine wrote:
> > On Wed, Jun 14, 2023 at 6:15 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> >>>> Any known issues in pg 14.8 that would trigger this behaviour?
> >>>
> >>> Yes, there are known issues with memory handling in logical
> >>> replication setups. See for example this thread:
> >>>
> >>> https://www.postgresql.org/message-id/CAMnUB3oYugXCBLSkih+qNsWQPciEwos6g_AMbnz_peNoxfHwyw@mail.gmail.com
> >>
> >> Why would 14.8 have made that problem worse?
>
> Hmm? I don't necessarily imply that 14.8 made it worse, but that
> there are known issues in this area as the other thread mention (which
> is mainly about v15, actually, where the situation could be a bit
> better).
Yeah, IIUC the logical decoding could use nearly unlimited memory
depending on workloads (see analysis here[1]).
Regards,
--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2023-06-15 04:04:22 | BUG #17977: PorstGreSQL in a jail crashes randomly with Signal 10 bus error |
| Previous Message | Michael Guissine | 2023-06-15 01:06:42 | Re: BUG #17974: Walsenders memory usage suddenly spike to 80G+ causing OOM and server reboot |