valgrind on initdb

From: Jesper Pedersen <jesper(dot)pedersen(at)redhat(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: valgrind on initdb
Date: 2018-11-07 13:08:15
Message-ID: 3fe1e38a-fb70-6260-9300-ce67ede21c32@redhat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

While looking at [1] (included in 23315.log) there are other warnings as
well.

I ran with

valgrind --leak-check=full --show-leak-kinds=all --gen-suppressions=all
--suppressions=/path/to/postgresql/src/tools/valgrind.supp
--time-stamp=yes --log-file=/tmp/valgrind/%p.log --trace-children=yes
--track-origins=yes --read-var-info=yes initdb -D /tmp/pgsql --no-clean
--no-sync --no-locale 2>&1 | tee /tmp/valgrind/initdb.log

[1]
https://www.postgresql.org/message-id/cb062f4d-55b8-28be-b55f-2e593a3b3755%40redhat.com

Best regards,
Jesper

Attachment Content-Type Size
initdb.tgz application/x-compressed-tar 45.2 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2018-11-07 13:21:59 Re: Support custom socket directory in pg_upgrade
Previous Message Pavel Raiskup 2018-11-07 12:55:57 Re: plruby: rb_iterate symbol clash with libruby.so