X-Original-To: pgsql-committers@postgresql.org Received: from houston.familyhealth.com.au (unknown [203.59.48.253]) by postgresql.org (Postfix) with ESMTP id E6091475C15 for ; Mon, 10 Mar 2003 23:17:43 -0500 (EST) Received: (from root@localhost) by houston.familyhealth.com.au (8.11.6/8.11.6) id h2B4Hmn10386 for pgsql-committers@postgresql.org; Tue, 11 Mar 2003 12:17:48 +0800 (WST) (envelope-from chriskl@familyhealth.com.au) Received: from mariner (mariner.internal [192.168.0.101]) by houston.familyhealth.com.au (8.11.6/8.9.3) with SMTP id h2B4Hg710206; Tue, 11 Mar 2003 12:17:42 +0800 (WST) Message-ID: <018201c2e785$2c12c750$6500a8c0@fhp.internal> From: "Christopher Kings-Lynne" To: "Sean Chittenden" , "Marc G. Fournier" Cc: "Tom Lane" , References: <20030306031656.1876F4762E0@postgresql.org> <032f01c2e390$b1842b20$6500a8c0@fhp.internal> <11077.1046921667@sss.pgh.pa.us> <033f01c2e392$71476570$6500a8c0@fhp.internal> <12228.1046922471@sss.pgh.pa.us> <20030306094117.GA79234@perrin.int.nxad.com> <20030310224706.T35660@hub.org> <20030311041133.GC79234@perrin.int.nxad.com> Subject: Re: pgsql-server/ /configure /configure.in rc/incl ... Date: Tue, 11 Mar 2003 12:17:46 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-scanner: scanned by Inflex 0.1.5c - (http://www.inflex.co.za/) X-Archive-Number: 200303/59 X-Sequence-Number: 9302 > > I would personally be interested in seeing patches ... what would be > > involved? > > Whoa! Surprisingly, much less than I expected!!! A small shim would > have to be put in place to abstract away returning valid file > descriptors that are ready to be read()/write(). What's really cool, > is there are only a handful of places that'd have to be updated (as > far as I can tell): It would be nice to have this support there, however Tom was correct in saying it really only applies to network apps that are handling thousands of connections, all really, really fast. Postgres doesn't. I say you'd have to do the work, then do the benchmarking to see if it makes a difference. Chris