Re: pgsql-server/ /configure /configure.in rc/incl ...
| От | Tom Lane |
|---|---|
| Тема | Re: pgsql-server/ /configure /configure.in rc/incl ... |
| Дата | |
| Msg-id | 12228.1046922471@sss.pgh.pa.us обсуждение |
| Ответ на | Re: pgsql-server/ /configure /configure.in rc/incl ... ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>) |
| Ответы |
Re: pgsql-server/ /configure /configure.in rc/incl ...
Re: pgsql-server/ /configure /configure.in rc/incl ... |
| Список | pgsql-committers |
"Christopher Kings-Lynne" <chriskl@familyhealth.com.au> writes:
>>> Has anyone ever thought about adding kqueue (for *BSD) support to
>>> Postgres, instead of using select?
>>
>> Why? poll() is standard. kqueue isn't, AFAIK.
> It's supposed be a whole heap faster - there is no polling involved...
Supposed by whom? Faster than what? And how would it not poll?
The way libpq uses this call, it's either probing for current status
(timeout=0) or it's willing to block, possibly indefinitely, until the
desired condition arises. It does not sit there in a busy-wait loop.
I can't see any reason to think that an OS-specific API would give
any marked difference in performance.
regards, tom lane
В списке pgsql-committers по дате отправления: