No one should care of this but to make shure..
At Tue, 29 Mar 2016 20:12:03 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp> wrote in
<20160329.201203.78219296.horiguchi.kyotaro@lab.ntt.co.jp>
> By the way, memory blocks that readline sees are freed by it but
> blocks allocated by the additional pstrdup seems abandoned
> without being freed. Actually, the address of newly allocated
> blocks seems increasing time by time slowly *even without this
> patch*..
psql doesn't leak memory. The increment was the result of new
history entry. src/common/exec.c does the following thing,
./common/exec.c:586: putenv(strdup(env_path));
./common/exec.c:597: putenv(strdup(env_path));
valgrind complains that the memory block allocated there is
definitely lost but it seems to be called once in lifetime of a
process.
regards,
--
Kyotaro Horiguchi
NTT Open Source Software Center
