On Fri, Feb 10, 2023 at 10:04 AM Tom Lane <tgl@xxxxxxxxxxxxx> wrote: > > =?UTF-8?Q?Jon_Erdman?= <jon@xxxxxxxxxxxxxxxxxx> writes: > > I've got a background worker that has a slow memory leak in it > > somewhere. How can I get it to start under valgrind to get a memcheck > > output from it? > > You have to valgrind the whole cluster AFAIK. Basically, start > the postmaster under valgrind with --trace-children=yes. > For leak tracking you probably also want > --leak-check=full --track-origins=yes --read-var-info=yes One additional comment... the program in question and PostgreSQL should also be built with -g -O1 per https://valgrind.org/docs/manual/quick-start.html . Otherwise, there's a risk the line information will not be accurate or usable. Jeff
