Re: Report a potential memory leak in PostgresSQL 14.1

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: wliang(at)stu(dot)xidian(dot)edu(dot)cn
Cc: pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Report a potential memory leak in PostgresSQL 14.1
Date: 2022-02-14 12:20:18
Message-ID: 5374E2C6-891C-4303-A743-E39306E7F72D@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 14 Feb 2022, at 11:02, wliang(at)stu(dot)xidian(dot)edu(dot)cn wrote:

Thanks for you report.

> 4112 AssignDumpId(&pubrinfo[j].dobj);

AssignDumpId records the DumpableObject and keeps a reference to this memory,
have a read of that function and I think you'll see how the memory is managed.

--
Daniel Gustafsson https://vmware.com/

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Delaney, Ed 2022-02-14 22:50:06 Postgres 13.5 out parameter argument with explicit cast fails with argument is not writable
Previous Message wliang 2022-02-14 10:02:42 Report a potential memory leak in PostgresSQL 14.1