Re: [PATCH] ecpg: fix progname memory leak - Mailing list pgsql-hackers

From John Naylor
Subject Re: [PATCH] ecpg: fix progname memory leak
Date
Msg-id CAFBsxsHbqMzDoGB3eAGmpcpB+7uae+LLi_G+o8HMEECM9CbQcQ@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] ecpg: fix progname memory leak  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers


On Fri, Oct 9, 2020 at 12:50 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Consulting the wiki page's edit history shows that Bruce has been
doing some maintenance work, but almost nobody else does.  Evidently
that's not enough.

I'd be +1 for the "aggressive culling" suggested upthread, but
I'm not particularly volunteering to do it, either.

I'll start a separate thread for this. Working on one or a small number of sections at a time should be manageable.

--
John Naylor
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company 

pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: pg_upgrade: fail early if a tablespace dir already exists for new cluster version
Next
From: Tom Lane
Date:
Subject: Re: BUG #15858: could not stat file - over 4GB