Re: Sync Rep v17

Поиск
Список
Период
Сортировка
От Simon Riggs
Тема Re: Sync Rep v17
Дата
Msg-id 1298967674.12992.3210.camel@ebony
обсуждение исходный текст
Ответ на Re: Sync Rep v17  (Fujii Masao <masao.fujii@gmail.com>)
Ответы Re: Sync Rep v17
Re: Sync Rep v17
Re: Sync Rep v17
Список pgsql-hackers
On Tue, 2011-03-01 at 15:51 +0900, Fujii Masao wrote:
> Thanks for update of the patch!
> 
> On Tue, Mar 1, 2011 at 3:40 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
> >> SyncRepRemoveFromQueue seems not to be as short-term as we can
> >> use the spinlock. Instead, LW lock should be used there.
> 
> You seem to have forgotten to fix the above-mentioned issue.

Not forgotten.

> A spinlock can be used only for very short-term operation like
> read/write of some shared-variables. The operation on the queue
> is not short, so should be protected by LWLock, I think.

There's no need to sleep while holding locks and the operations are very
short in most cases. The code around it isn't trivial, but that's no
reason to use LWlocks.

LWlocks are just spinlocks plus sem sleeps, so I don't see the need for
that in the current code. Other views welcome.

-- Simon Riggs           http://www.2ndQuadrant.com/books/PostgreSQL Development, 24x7 Support, Training and Services



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: Sync Rep v17
Следующее
От: Simon Riggs
Дата:
Сообщение: Re: Sync Rep v17