Re: Report a potential memory leak in setup_config()

Andres Freund <andres@anarazel.de> writes:
> I was pondering initdb's design a bunch lately. So I started a -hackers thread:
> https://postgr.es/m/20220216021219.ygzrtb3hd5bn7olz%40alap3.anarazel.de

Yeah, I read that.  I think making the backend read these files directly
makes a ton of sense, so I'm no longer very excited about improving the
performance or memory consumption of the replace_token stuff.  I think
we should put this thread on hold until someone does that, and then
maybe take another look to see if initdb still leaks anything worth
worrying about.

            regards, tom lane