From: | Jon Erdman <jon(at)thewickedtribe(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, noloader(at)gmail(dot)com <noloader(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: valgrind a background worker |
Date: | 2023-02-11 03:08:59 |
Message-ID: | 010101863e728abb-2adafcc0-e579-4430-a6cb-8791eb056f3d-000000@us-west-2.amazonses.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2/10/23 3:05 PM, Tom Lane wrote:
> 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.
Thanks much both of you! I'll report back how it goes ;)
--
Jon Erdman (aka StuckMojo)
PostgreSQL Zealot
From | Date | Subject | |
---|---|---|---|
Next Message | Andrus | 2023-02-11 10:10:25 | How to pass table column values to function |
Previous Message | Tom Lane | 2023-02-10 21:05:10 | Re: valgrind a background worker |