Re: valgrind a background worker
От | Tom Lane |
---|---|
Тема | Re: valgrind a background worker |
Дата | |
Msg-id | 231809.1676063110@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: valgrind a background worker (Jeffrey Walton <noloader@gmail.com>) |
Ответы |
Re: valgrind a background worker
|
Список | pgsql-general |
Jeffrey Walton <noloader@gmail.com> writes: > On Fri, Feb 10, 2023 at 10:04 AM Tom Lane <tgl@sss.pgh.pa.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
В списке pgsql-general по дате отправления: