RE: memory leak in logical WAL sender with pgoutput's cachectx

From: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
To: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, 'Masahiko Sawada' <sawada(dot)mshk(at)gmail(dot)com>
Cc: "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, Xuneng Zhou <xunengzhou(at)gmail(dot)com>, 赵宇鹏(宇彭) <zhaoyupeng(dot)zyp(at)alibaba-inc(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: RE: memory leak in logical WAL sender with pgoutput's cachectx
Date: 2025-08-21 05:41:09
Message-ID: OSCPR01MB14966E2AC19D8B9D9BA5FDDFDF532A@OSCPR01MB14966.jpnprd01.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Firstly I also considered but did not choose because of the code complexity.
> After considering more, it is not so difficult, PSA new file.

v3 contained 100_cachectm_oom.pl, which won't succeed. Here is a patch
which removed the test file.

Best regards,
Hayato Kuroda
FUJITSU LIMITED

Attachment Content-Type Size
v4-0001-pgoutput-allow-cleaning-up-Relsync-cache-entries.patch application/octet-stream 10.5 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-08-21 05:45:41 Re: Redesigning postmaster death handling
Previous Message Tom Lane 2025-08-21 05:28:04 Re: Redesigning postmaster death handling