From: wliang@stu.xidian.edu.cn
To: Julien Rouhaud <rjuju123@gmail.com>
Cc: pgsql-bugs <pgsql-bugs@lists.postgresql.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: david.g.johnston@gmail.com
Subject: Re: Re: Re all: Report some potential memory leak bugs in pg_dump.c
Date: Sat, 19 Feb 2022 20:29:59 +0800 (GMT+08:00)
Message-ID: <2ef4e895.13e4.17f11f5dcd3.Coremail.wliang@stu.xidian.edu.cn> (raw)
In-Reply-To: <20220219111005.57bfn4qshuqxzkzi@jrouhaud>
References: <1f102fb7.f70.17f1102ec92.Coremail.wliang@stu.xidian.edu.cn>
<20220219111005.57bfn4qshuqxzkzi@jrouhaud>
> Indeed this function doesn't cache anything and explicitly calls pg_strdup.
>
> Here the amount of leaked memory is likely to be very small (I never heard of
> people having thousands of text search templates or parsers), and pg_dump isn't
> a long lived process so probably no one thought it was worth to extra code to
> free that memory, which I agree with.
Thank you for your conformation.
I am also grateful for your patient explanation to what I don't understand.
Thank you all.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: wliang@stu.xidian.edu.cn, rjuju123@gmail.com, pgsql-bugs@lists.postgresql.org, tgl@sss.pgh.pa.us, david.g.johnston@gmail.com
Subject: Re: Re: Re all: Report some potential memory leak bugs in pg_dump.c
In-Reply-To: <2ef4e895.13e4.17f11f5dcd3.Coremail.wliang@stu.xidian.edu.cn>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox