pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: sunqiankun@highgo.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16273: InitDB Memory leak
Date: Sun, 23 Feb 2020 01:43:26 -0500
Message-ID: <28473.1582440206@sss.pgh.pa.us> (raw)
In-Reply-To: <16273-9ebc6c641602e0a5@postgresql.org>
References: <16273-9ebc6c641602e0a5@postgresql.org>

PG Bug reporting form <noreply@postgresql.org> writes:
> when i read the code  in src/bin/initdb/initdb.c.
> At the function: set_info_version, we use pg_strdup to malloc  memory, but
> we don't free it.

There are lots of minor memory leaks in initdb.  We don't really care
that much, because the program executes over a fixed set of data and
then terminates.

			regards, tom lane





view thread (2+ messages)

Message-ID: <28473.1582440206@sss.pgh.pa.us>
Permalink:  ../28473.1582440206@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/28473.1582440206@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, sunqiankun@highgo.com
  Subject: Re: BUG #16273: InitDB Memory leak
  In-Reply-To: <28473.1582440206@sss.pgh.pa.us>
  References: <16273-9ebc6c641602e0a5@postgresql.org> <28473.1582440206@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox