Re: LISTEN / NOTIFY performance in 8.3

Поиск
Список
Период
Сортировка
От James Mansion
Тема Re: LISTEN / NOTIFY performance in 8.3
Дата
Msg-id 47C48F9E.7000505@mansionfamily.plus.com
обсуждение исходный текст
Ответ на Re: LISTEN / NOTIFY performance in 8.3  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: LISTEN / NOTIFY performance in 8.3  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-performance
Tom Lane wrote:
> read-modify-write type of operation it uses an exclusive lock, so only
> one can clear its pg_listener entry at a time.  The 'waiting' ones you
> are seeing are stacked up behind whichever one has the lock at the
> moment.  They shouldn't be waiting for long.
>
I certainly hadn't expected that to be the implementation technique -
isn't it smply that we need
a sngle flag per worker process and can set/test-and-clear with atomic
operations and then a
signal to wake them up?

Anyway - how hard would it be to install triggers on commit and
rollback?  Then we could write
our own mechanisms.

James


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

Предыдущее
От: "Joshua D. Drake"
Дата:
Сообщение: Re: disabling an index without deleting it?
Следующее
От: Tom Lane
Дата:
Сообщение: Re: LISTEN / NOTIFY performance in 8.3