Re: Re: Re all: Report some potential memory leak bugs in pg_dump.c

From: wliang(at)stu(dot)xidian(dot)edu(dot)cn
To: "Julien Rouhaud" <rjuju123(at)gmail(dot)com>
Cc: pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, david(dot)g(dot)johnston(at)gmail(dot)com
Subject: Re: Re: Re all: Report some potential memory leak bugs in pg_dump.c
Date: 2022-02-19 12:29:59
Message-ID: 2ef4e895.13e4.17f11f5dcd3.Coremail.wliang@stu.xidian.edu.cn
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


> 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.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2022-02-19 16:49:48 Re: Re all: Report some potential memory leak bugs in pg_dump.c
Previous Message Julien Rouhaud 2022-02-19 11:10:05 Re: Re all: Report some potential memory leak bugs in pg_dump.c