| From: | Jeffrey Walton <noloader(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jon Erdman <jon(at)thewickedtribe(dot)net>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: valgrind a background worker |
| Date: | 2023-02-10 20:58:35 |
| Message-ID: | CAH8yC8kzfRCW_Q+mWAG-+eMNr0piLwXFg76eHDNupzndN3g=uw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Feb 10, 2023 at 10:04 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> =?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
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-02-10 21:05:10 | Re: valgrind a background worker |
| Previous Message | Adrian Klaver | 2023-02-10 20:07:57 | Re: PostgreSQL 13.9.3 Uninstall fails with "Unable to initialize any installation mode" |