Re: Memory leak in pg_logical_slot_{get,peek}_changes
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: vignesh C <vignesh21@gmail.com>
Cc: "Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-01-07T23:49:48Z
Lists: pgsql-hackers
On Mon, Dec 30, 2024 at 10:31:20PM +0530, vignesh C wrote: > The attached v3 version has the changes for the same. I have verified > the patch in PG14 and PG13 by attaching to the debugger and calling > "call MemoryContextStats(CacheMemoryContext)" to see there are no > leaks. Sorry for the delay here, I have come back into the business. I have tuned a bit the comment block on top of the declaration of the two contexts, fixed a comment in maybe_send_schema() that was now inexact, and applied that down to v13 and v14. -- Michael
Commits
-
Fix memory leak in pgoutput with relation attribute map
- a786cf04df76 13.19 landed
- c53d90bb47ae 14.16 landed
- da8bd5d424e0 15.11 landed
- e3a27fd06d06 16.7 landed
- 836435424ba8 17.3 landed
- c9b3d4909bbf 18.0 landed
-
Fix memory leak in pgoutput with publication list cache
- cfd6cbcf9be0 14.16 cited