pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron Mayer <rm_pg@cheapcomplexdevices.com>
To: Merlin Moncure <merlin.moncure@rcsonline.com>
Subject: Re: seq scan cache vs. index cache smackdown
Date: Mon, 21 Feb 2005 17:14:19 -0800
Message-ID: <421A876B.6010308@cheapcomplexdevices.com> (raw)
In-Reply-To: <6EE64EF3AB31D5448D0007DD34EEB3412A762F@Herge.rcsinc.local>
References: <6EE64EF3AB31D5448D0007DD34EEB3412A762F@Herge.rcsinc.local>

Merlin Moncure wrote:
> 
> readv and writev are in the single unix spec...and yes ...
> 
> On some systems they might just be implemented as a loop inside the
> library, or even as a macro.

You sure?

Requirements like this:
  http://www.opengroup.org/onlinepubs/007908799/xsh/write.html
  "Write requests of {PIPE_BUF} bytes or less will not be
   interleaved with data from other processes doing writes
   on the same pipe."
make me think that it couldn't be just a macro; and if it
were a loop in the library it seems it'd still have to
make sure it's done with a single write system call.

(yeah, I know that requirement is just for pipes; and I
suppose they could write a loop for normal files and a
different special case for pipes; but I'd be surprised).



view thread (24+ messages)  latest in thread

Message-ID: <421A876B.6010308@cheapcomplexdevices.com>
Permalink:  ../421A876B.6010308@cheapcomplexdevices.com/
Also on:    postgresql.org/message-id/421A876B.6010308@cheapcomplexdevices.com

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: rm_pg@cheapcomplexdevices.com, merlin.moncure@rcsonline.com
  Subject: Re: seq scan cache vs. index cache smackdown
  In-Reply-To: <421A876B.6010308@cheapcomplexdevices.com>

* 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