Re: LISTEN / NOTIFY performance in 8.3
| От | Tom Lane |
|---|---|
| Тема | Re: LISTEN / NOTIFY performance in 8.3 |
| Дата | |
| Msg-id | 9940.1204068830@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: LISTEN / NOTIFY performance in 8.3 (James Mansion <james@mansionfamily.plus.com>) |
| Ответы |
Re: LISTEN / NOTIFY performance in 8.3
|
| Список | pgsql-performance |
James Mansion <james@mansionfamily.plus.com> writes:
> 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?
Hardly --- how's that going to pass a notify name? Also, a lot of
people want some payload data in a notify, not just a condition name;
any reimplementation that doesn't address that desire probably won't
get accepted.
There's lots of threads in the -hackers archives about reimplementing
listen/notify in a saner fashion. Personally I lean towards using
something much like the sinval queue.
regards, tom lane
В списке pgsql-performance по дате отправления: