Hi, Child processes do not need the postmaster's working memory context and release it at the start of their main function. However, the slotsync worker appears to have missed this step.
To avoid this unnecessary memory usage, I'd like to propose that the slotsync
worker release the postmaster's working memory context at startup.
A patch is attached.
Currently, pg_log_backend_memory_contexts() reports the following
postmaster-related memory contexts in the slotsync worker:
LOG: level: 2; Postmaster: 21984 total in 2 blocks; 5600 free (7
chunks); 16384 used
LOG: level: 3; ident parser context: 1024 total in 1 blocks; 784
free (0 chunks); 240 used
LOG: level: 3; hba parser context: 25600 total in 6 blocks; 9864
free (11 chunks); 15736 used
With the attached patch, these contexts are no longer present.
Regards,
--
Fujii Masao
v1-0001-Release-postmaster-working-memory-context-in-slot.patch
Description: Binary data
