Re: [PATCH] Memory leak in pg_config

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Raúl Marín Rodríguez <rmrodriguez(at)carto(dot)com>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Memory leak in pg_config
Date: 2018-11-14 14:59:57
Message-ID: 6394.1542207597@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

=?UTF-8?B?UmHDumwgTWFyw61uIFJvZHLDrWd1ZXo=?= <rmrodriguez(at)carto(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Evgeniy Efimkin 2018-11-14 15:10:46 Re: [WIP] Special role for subscriptions
Previous Message Ronan Dunklau 2018-11-14 14:43:33 Parametrization and UNION in view