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
React, useEffect, and Stale Closures: How to Avoid Them with Dependencies and useRef
Jivbcoop • 4 votes
2
Better react-hook-form Smart Form Components
Maarten Hus • 2 votes
3
AGI, ASI, A*I – Do we have all we need to get there?
John D. Cook • 1 votes
4
Quoting Thariq Shihipar
Simon Willison • 1 votes
5
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft • 1 votes
6
Using Browser Apis In React Practical Guide
Jivbcoop • 1 votes