> >Thanks for your close attention to Firebird allocator.
> >I'll address the issues you noticed soon. I.e.
> >1) replace B+ tree used to manage memory fragments with=20
> static vector=20
> >of doubly linked list pointers (similar to one used in=20
> vulcan to cache=20
> >small thingies) and bitmap index for quick searching in it
> >2) add red zones checking to make debugging happier on=20
> platforms which=20
> >do not have memory debugging facilities
> >3) publish code which makes Valgrind aware of Firebird=20
> memory pools and=20
> >allows it to detect all kinds of memory problems including invalid=20
> >I.e. basically I'll marry the approaches to create=20
> nice-looking hybrid.
> > =20
> Nickolay, you had no interest in any of this until I went=20
> through the trouble and bother of writing a replacement. But=20
> now that's done. =20
> Please try your hand at something else.
Thank you for the kind advice. Not sure that I will follow it, but
thanks anyway. :-)