| |||||||||||||
How 3.6 nearly broke PostgreSQLHow 3.6 nearly broke PostgreSQLPosted Oct 5, 2012 20:45 UTC (Fri) by jhoblitt (subscriber, #77733)In reply to: How 3.6 nearly broke PostgreSQL by cmccabe Parent article: How 3.6 nearly broke PostgreSQL
Couldn't libpthreads notify the kernel that pthread_spin_lock() is in use? You certainly wouldn't want to introduce a system call on every use but having to branch on the first use by a given pid shouldn't be too expensive.
(Log in to post comments)
|
|||||||||||||