=?UTF-8?Q?Jon_Erdman?= <jon(at)thewickedtribe(dot)net> 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
regards, tom lane