Re: Optimize duplicate code and fix memory leak in function fetch_remote_table_info() - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Optimize duplicate code and fix memory leak in function fetch_remote_table_info()
Date
Msg-id 2914135.1705725261@sss.pgh.pa.us
Whole thread Raw
In response to Re: Optimize duplicate code and fix memory leak in function fetch_remote_table_info()  (Yongtao Huang <yongtaoh2022@gmail.com>)
Responses Re: Optimize duplicate code and fix memory leak in function fetch_remote_table_info()
List pgsql-hackers
Yongtao Huang <yongtaoh2022@gmail.com> writes:
> (1)  I think *pfree(pub_names.data)* is necessary.

Really?

It looks to me like copy_table, and thence fetch_remote_table_info,
is called once within a transaction.  So whatever it leaks will be
released at transaction end.  This is a good thing, because it's
messy enough that I seriously doubt that there aren't other leaks
in it, or that it'd be practical to expect that it can be made
to never leak anything.

If anything, I'd be inclined to remove the random pfree's that
are in it now.  It's unlikely that they constitute a net win
compared to allowing memory context reset to clean things up.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Yongtao Huang
Date:
Subject: Re: Optimize duplicate code and fix memory leak in function fetch_remote_table_info()
Next
From: Dilip Kumar
Date:
Subject: Re: Synchronizing slots from primary to standby