From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Coverity reports looking good |
Date: | 2006-08-20 15:52:53 |
Message-ID: | 27601.1156089173@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> Whats basically left is a large number of memory leaks in frontend
> applications such as pg_dump, initdb, pg_ctl, etc. These haven't ever
> really been a priority (buildACLCommands is really bad in this
> respect).
Well, if Coverity's idea of good programming practice is that every
program must explicitly free everything it ever malloced before it
terminates, then I'm afraid we'll have to agree to disagree. The
above is nothing but make-work as far as programs with short intended
runtimes go. A leak in psql would be interesting if it can accumulate
across command-execution cycles, but I have zero interest in "cleaning
up" any of the programs mentioned above.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-08-20 15:53:05 | Re: Coverity reports looking good |
Previous Message | Michael Meskes | 2006-08-20 15:48:11 | Re: Coverity reports looking good |