Horton
Menu

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

Nils Goroll <slink@schokola.de>

View thread
From: Nils Goroll <slink@schokola.de>
To: Merlin Moncure <mmoncure@gmail.com>
Cc: pgsql-hackers@postgresql.org
Date: 2012-06-26T19:05:12Z
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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Reduce sinval synchronization overhead.