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 D4FE5474E53 for ; Wed, 5 Mar 2003 23:19:17 -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 h264JHx6012401; Wed, 5 Mar 2003 23:19:17 -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 23:19:16 -0500 Message-ID: <12400.1046924356@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200303/19 X-Sequence-Number: 9262 "Christopher Kings-Lynne" writes: > It's supposed be a whole heap faster - there is no polling involved... I looked into this more. AFAICT, the scenario in which kqueue is said to be faster involves watching a large number of file descriptors simultaneously. Since libpq is only watching one descriptor, I don't see the benefit of adopting kqueue ... regards, tom lane