On 10/06/15 16:05, Andres Freund wrote: > it'll nearly always be beneficial to spin
Trouble is that postgres cannot know if the process holding the lock actually does run, so if it doesn't, all we're doing is burn cycles and make the problem worse. Contrary to that, the kernel does know, so for a (f|m)utex which fails to acquire immediately and thus needs to syscall, the kernel has the option to spin only if the lock holder is running (the "adaptive" mutex). Nils -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
