"Jignesh K. Shah" <[EMAIL PROTECTED]> writes: > What its saying is that there are holds/waits in trying to get locks > which are locked at Solaris user library levels called from the > postgresql functions: > For example both the following functions are hitting on the same mutex > lock 0x10059e280 in Solaris Library call: > postgres`AllocSetDelete+0x98 > postgres`AllocSetAlloc+0x1c4
That's a perfect example of the sort of useless overhead that I was complaining of just now in pgsql-patches. Having malloc/free use an internal mutex is necessary in multi-threaded programs, but the backend isn't multi-threaded. And yet, apparently you can't turn that off in Solaris. (Fortunately, the palloc layer is probably insulating us from malloc's performance enough that this isn't a huge deal. But it's annoying.) regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly