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

Поиск
Список
Период
Сортировка
От Nils Goroll
Тема Re: why roll-your-own s_lock? / improving scalability
Дата
Msg-id 4FEA07E8.6020904@schokola.de
обсуждение исходный текст
Ответ на Re: why roll-your-own s_lock? / improving scalability  (Merlin Moncure <mmoncure@gmail.com>)
Список 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 по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: why roll-your-own s_lock? / improving scalability
Следующее
От: Nils Goroll
Дата:
Сообщение: Re: why roll-your-own s_lock? / improving scalability