Phil Eaton • 3/27/2024

Finding memory leaks in Postgres C code

Read Original

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
Finding memory leaks in Postgres C code

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
The Beautiful Web
Jens Oliver Meiert • 2 votes
2
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane • 1 votes
3
LLM Use in the Python Source Code
Miguel Grinberg • 1 votes
4
Wagon’s algorithm in Python
John D. Cook • 1 votes
5
An example conversation with Claude Code
Dumm Zeuch • 1 votes