Re: pgsql-server/ /configure /configure.in rc/incl ... - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql-server/ /configure /configure.in rc/incl ...
Date
Msg-id 12228.1046922471@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql-server/ /configure /configure.in rc/incl ...  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
Responses Re: pgsql-server/ /configure /configure.in rc/incl ...
Re: pgsql-server/ /configure /configure.in rc/incl ...
List 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 by date:

Previous
From: "Christopher Kings-Lynne"
Date:
Subject: Re: pgsql-server/ /configure /configure.in rc/incl ...
Next
From: Tom Lane
Date:
Subject: Re: pgsql-server/ /configure /configure.in rc/incl ...