On Solaris we want to use libumem or mtmalloc, so check for those. On Solaris there are lots of malloc implementations.  According to umem_alloc(3MALLOC):          ?  The malloc(3C), bsdmalloc(3MALLOC), and malloc(3MALLOC)  functions             have no support for concurrency. The libumem and mtmalloc(3MALLOC)             functions support concurrent allocations.
On Solaris we want to use libumem or mtmalloc, so check for those.
On Solaris there are lots of malloc implementations.  According to
umem_alloc(3MALLOC):
         ?  The malloc(3C), bsdmalloc(3MALLOC), and malloc(3MALLOC)  functions
            have no support for concurrency. The libumem and mtmalloc(3MALLOC)
            functions support concurrent allocations.

         ?  The bsdmalloc(3MALLOC) functions afford better performance but are
            space-inefficient.

         ?  The  malloc(3MALLOC) functions are space-efficient but have slower
            performance.

         ?  The standard,  fully  SCD-compliant  malloc(3C)  functions  are  a
            trade-off between performance and space-efficiency.

         ?  The  mtmalloc(3MALLOC) functions provide fast, concurrent malloc()
            implementations that are not space-efficient.

         ?  The  libumem  functions  provide  a  fast,  concurrent  allocation
            implementation  that  in  most  cases is more space-efficient than
            mtmalloc(3MALLOC).
So we want libumem if available, or else mtmalloc.

zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb