Henry B. Hotz wrote:
> The priorities seem obvious to me: 1) fix the array bounds problems. (If
> the fix is found after the 6.1 release then *immediately* release patches
> and/or version 6.1.1.) 2) Fix memory leaks in the parent PostMaster.
> (Make a 6.2 release ASAP.) 3) Fix memory leaks in the child processes,
> unless they can be determined to be unimportant for any conceivable
> transaction.
>
> I wouldn't normally go on at this length, except that I detect some
> ambivalence in the developer's posts on the subject. I hope that
> ambivalence is just an uncertainty in how to deal with the memory problems
> given the immaturity of the freeware tools, and not a desire to deny their
> seriousness.
Henry, my first reaction was probably pretty similar to yours but:
1) postgres is already in _successful_ use
2) the latest release is more solid than the last
3) _all_ the code is inherited, and is something of an unknown quantity
4) if the development team waited until the software were perfect, we
would have never seen it and probably never would.
btw, Henry and I work at the place, although we've never met. It's
interesting seeing the somewhat different approach the postgres
developers must take for this to be successful.
- Tom
------------------------------
