Hi Merlin,

> _POSIX_THREAD_PROCESS_SHARED

sure.

> Also, it's forbidden to do things like invoke i/o in the backend while
> holding only a spinlock. As to your larger point, it's an interesting
> assertion -- some data to back it up would help.

Let's see if I can get any. ATM I've only got indications, but no proof.

Nils

In response to

• Re: why roll-your-own s_lock? / improving scalability at 2012-06-26 18:46:06 from Merlin Moncure

pgsql-hackers by date

Next:	From: Nils Goroll	Date: 2012-06-26 19:06:02
	Subject: Re: why roll-your-own s_lock? / improving scalability
Previous:	From: Tom Lane	Date: 2012-06-26 18:50:51
	Subject: Re: why roll-your-own s_lock? / improving scalability