Phil Eaton • 3/27/2024

Finding memory leaks in Postgres C code

The article details the author's experience debugging a memory leak in Postgres's WAL Sender process. It explains the limitations of Valgrind for runtime leaks and demonstrates how to use the `memleak` program from the bcc tools to get stack traces of leaks in a running program without modifying its source code, using a contrived Postgres leak as an example.

0 comments

#debugging #postgres #c programming