X-Original-To: pgsql-committers@postgresql.org Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 3A9CE475FEE for ; Wed, 5 Mar 2003 22:47:52 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.8/8.12.8) with ESMTP id h263lqx6012229; Wed, 5 Mar 2003 22:47:52 -0500 (EST) To: "Christopher Kings-Lynne" Cc: pgsql-committers@postgresql.org Subject: Re: pgsql-server/ /configure /configure.in rc/incl ... In-reply-to: <033f01c2e392$71476570$6500a8c0@fhp.internal> References: <20030306031656.1876F4762E0@postgresql.org> <032f01c2e390$b1842b20$6500a8c0@fhp.internal> <11077.1046921667@sss.pgh.pa.us> <033f01c2e392$71476570$6500a8c0@fhp.internal> Comments: In-reply-to "Christopher Kings-Lynne" message dated "Thu, 06 Mar 2003 11:42:42 +0800" Date: Wed, 05 Mar 2003 22:47:51 -0500 Message-ID: <12228.1046922471@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200303/18 X-Sequence-Number: 9261 "Christopher Kings-Lynne" 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