pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: pgsql-committers@postgresql.org
Subject: Re: pgsql-server/ /configure /configure.in rc/incl ...
Date: Wed, 5 Mar 2003 23:33:36 -0500 (EST)
Message-ID: <200303060433.h264XaQ11718@candle.pha.pa.us> (raw)
In-Reply-To: <12228.1046922471@sss.pgh.pa.us>


I assume he just assumed poll() actually polls.  I doesn't.  It is just
like select().


---------------------------------------------------------------------------

Tom Lane wrote:
> "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
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073



view thread (22+ messages)  latest in thread

Message-ID: <200303060433.h264XaQ11718@candle.pha.pa.us>
Permalink:  ../200303060433.h264XaQ11718@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200303060433.h264XaQ11718@candle.pha.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, chriskl@familyhealth.com.au, pgsql-committers@postgresql.org
  Subject: Re: pgsql-server/ /configure /configure.in rc/incl ...
  In-Reply-To: <200303060433.h264XaQ11718@candle.pha.pa.us>
  References: <12228.1046922471@sss.pgh.pa.us> <200303060433.h264XaQ11718@candle.pha.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox