Niki Guldbrand wrote: > Hi Paul. > > Regarding bug 737 and 738. > > 737: > Have you had any time to look into this by any chance ? > Do you need more info, or any other way I can help with it ?
I looked at it. Looks trivial. Could you please do a git-pull and try again? The old data was retrieved as string rather than as a blob as it should be. I havent tested against postgresql since I don't have any 2.2. postgresql store available. > > 738: > Regarding this bug the main issues is fixed, no db connection leaks any > more, but I still see some memory leaking in imapd, and maybe also lmtp > (not sure about that one, as it's leaking so little, that it might be > part of normal memory growth) Fixing memory leakage using valgrind runs is a normal part of my QA process. This will continue until well into the 2.4 cycle I'm sure. If you can produce valgrind logs that demonstrate leakage please do. All help and patches are most welcome. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ Dbmail-dev mailing list [email protected] http://twister.fastxs.net/mailman/listinfo/dbmail-dev
