Re: [HACKERS] 6.1 issues resolved

I would guess purifying the backend should be an effor of every developer
who has purify....BTW: I just ran purify on pg_dump and it came out with a
ton of memory leaks (and 40% of potential leaks)...I 'll work on that
today...

=+=------------------------/\---------------------------------=+=
       Igor Natanzon      |**|   E-mail: igor@sba.miami.edu
=+=------------------------\/---------------------------------=+=

On Sun, 1 Jun 1997, Bruce Momjian wrote:

> >
> > I ran purify yesterday on psql, and it found several memory leaks in
> > libpq. I fixed a couple of them and will post a patch in a couple of
> > hours. Unfortunately I only have a signle terminal window for now so I
> > can't work on the backend but libpq is significant too..BTW: There is a
> > bug right now in psql:
> >     run psql.
> >     do \m to turn on monitor style output.
> >     select *  from some table...You should see (NULL) instead of
> >     the row separator....
> >
> > I fixed it too and will send a patch for it together with memory leak
> > patch (they are actually related)...
>
> That's great.  Glad you can help out.  psql/libpq are certainly
> important to Purify.
>
> The backend Purify is going to be ugly, I would guess, because it is so
> big.  Those memory issues are hard to find, and most of use don't have
> Purify to help.
>
> --
> Bruce Momjian
> maillist@candle.pha.pa.us
>

------------------------------