Re: [PATCH] Memory leak in pg_config - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCH] Memory leak in pg_config
Date
Msg-id 6394.1542207597@sss.pgh.pa.us
Whole thread Raw
In response to [PATCH] Memory leak in pg_config  (Raúl Marín Rodríguez <rmrodriguez@carto.com>)
Responses Re: [PATCH] Memory leak in pg_config
List pgsql-hackers
=?UTF-8?B?UmHDumwgTWFyw61uIFJvZHLDrWd1ZXo=?= <rmrodriguez@carto.com> writes:
> I've been trying to run Postgis regress tests under Clang sanitizers and one of
> the issues I'm facing is the constant stream of errors during the `configure`
> step coming from calls to `pg_config`.

TBH, I do not think we should do anything about this.  It has never been
project policy that short-lived programs should free everything before
exiting, and I don't think we should change that.  initdb, in particular,
would need a huge amount of work to meet such a policy, and it would
really be entirely wasted effort.  Just because you've configured your
tools to enforce an unreasonable policy doesn't make it a reasonable one.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Ronan Dunklau
Date:
Subject: Parametrization and UNION in view
Next
From: Evgeniy Efimkin
Date:
Subject: Re: [WIP] Special role for subscriptions