Skip site navigation (1) Skip section navigation (2)

Re: why roll-your-own s_lock? / improving scalability

From: Nils Goroll <slink(at)schokola(dot)de>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: why roll-your-own s_lock? / improving scalability
Date: 2012-06-26 19:05:12
Message-ID: 4FEA07E8.6020904@schokola.de (view raw or flat)
Thread:
Lists: 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

In response to

pgsql-hackers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group