RE: Memory leak in pg_logical_slot_{get,peek}_changes
Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
From: "Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>
To: vignesh C <vignesh21@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-12-27T08:13:53Z
Lists: pgsql-hackers
On Thursday, December 26, 2024 8:01 PM vignesh C <vignesh21@gmail.com> wrote: > > Here is an updated version which includes registers to reset the memory > context that is in-line with a recently committed patch at [1]. Thanks for updating patches ! They look good to me. Just to confirm, would the other stuff (streamed_txns) that allocated under CacheMemoryContext also leaks memory ? I think it's OK to change them separately if it does but just would like to confirm if there is a risk. > [1] - > https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=cfd6cbc > f9be078fbdf9587014231a5772039b386 Best Regards, Hou zj
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