Re: why roll-your-own s_lock? / improving scalability - Mailing list pgsql-hackers

From Nils Goroll
Subject Re: why roll-your-own s_lock? / improving scalability
Date
Msg-id 4FEA07E8.6020904@schokola.de
Whole thread Raw
In response to Re: why roll-your-own s_lock? / improving scalability  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: why roll-your-own s_lock? / improving scalability
Next
From: Nils Goroll
Date:
Subject: Re: why roll-your-own s_lock? / improving scalability