From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | noloader(at)gmail(dot)com |
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 21:05:10 |
Message-ID: | 231809.1676063110@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Jeffrey Walton <noloader(at)gmail(dot)com> writes:
> On Fri, Feb 10, 2023 at 10:04 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> 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.
Yeah. Also, you need to compile Postgres with -DUSE_VALGRIND
if you want valgrind to have any idea about palloc/pfree.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jon Erdman | 2023-02-11 03:08:59 | Re: valgrind a background worker |
Previous Message | Jeffrey Walton | 2023-02-10 20:58:35 | Re: valgrind a background worker |