On Sun, Aug 20, 2006 at 11:52:53AM -0400, Tom Lane wrote:
> Martijn van Oosterhout 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
On Sun, Aug 20, 2006 at 11:52:53AM -0400, Tom Lane wrote:
> 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
I don't think Coverity even knows
Martijn van Oosterhout wrote:
I thought I'd like to report that right now the Coverity reports are
looking good. There are no issues detected in either the backend code
or the ECPG library. For the latter I'd like the thank Joachim Wieland
and Michael Meskes for getting ECPG into shape.
Whats
Martijn van Oosterhout 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 pra
On Sun, Aug 20, 2006 at 03:49:24PM +0200, Martijn van Oosterhout wrote:
> 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).
> ...
> I
I thought I'd like to report that right now the Coverity reports are
looking good. There are no issues detected in either the backend code
or the ECPG library. For the latter I'd like the thank Joachim Wieland
and Michael Meskes for getting ECPG into shape.
Whats basically left is a large number o
