Re: valgrind on initdb

From: John Naylor <jcnaylor(at)gmail(dot)com>
To: jesper(dot)pedersen(at)redhat(dot)com
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: valgrind on initdb
Date: 2018-11-07 13:47:59
Message-ID: CAJVSVGUP0wJRwGMdCP+ayB_Gbv1280Y-yHLEd35H9A7yOy2+gg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11/7/18, Jesper Pedersen <jesper(dot)pedersen(at)redhat(dot)com> wrote:
> Hi,
>
> While looking at [1] (included in 23315.log) there are other warnings as
> well.

Perhaps it's worth revisiting to make debugging easier, but right now
initdb.c has this comment:

* Note:
* The program has some memory leakage - it isn't worth cleaning it up.

-John Naylor

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-11-07 13:51:25 Re: Connection limit doesn't work for superuser
Previous Message Daniel Gustafsson 2018-11-07 13:25:48 Re: Support custom socket directory in pg_upgrade