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

From Tom Lane
Subject Re: [PATCH] ecpg: fix progname memory leak
Date
Msg-id 2770341.1602262236@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCH] ecpg: fix progname memory leak  (Magnus Hagander <magnus@hagander.net>)
Responses Re: [PATCH] ecpg: fix progname memory leak  (Bruce Momjian <bruce@momjian.us>)
Re: [PATCH] ecpg: fix progname memory leak  (John Naylor <john.naylor@enterprisedb.com>)
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> That said, having this in a different format would in no way fix the fact
> that the information is mislabeled and obsolete.  It would likely be
> equally mislabeled and obsolete in an issue tracker. Just look at almost
> any of the other projects out there that *do* use an issue tracker and have
> been around for 20+ years.

The long and the short of it is that a list like this is only of value
if it gets diligently maintained.  Putting the data in a different tool
changes nothing about that.  (A tool might reduce the effort involved,
*if* it's a good match to your workflow.  But it won't reduce the effort
to zero.)

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.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Expansion of our checks for connection-loss errors
Next
From: Tomas Vondra
Date:
Subject: Re: Possible NULL dereferencing null pointer (src/backend/executor/nodeIncrementalSort.c)