Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id 05130476223 for ; Thu, 23 May 2002 11:23:41 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id E8FF8475B25 for ; Thu, 23 May 2002 10:50:34 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g4NEnDW05592; Thu, 23 May 2002 10:49:13 -0400 (EDT) To: "Nigel J. Andrews" Cc: "Command Prompt, Inc." , Steve Lane , jlx@commandprompt.com, pgsql-general@postgresql.org Subject: Re: MacOS X Shared Buffers (SHMMAX)? In-reply-to: References: Comments: In-reply-to "Nigel J. Andrews" message dated "Thu, 23 May 2002 15:09:53 +0100" Date: Thu, 23 May 2002 10:49:13 -0400 Message-ID: <5589.1022165353@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200205/826 X-Sequence-Number: 24806 "Nigel J. Andrews" writes: > My 'standard' way of doing this is to loop while the error is EAGAIN > but with a small retry counter to limit the number of attempts > made. Hopefully the second time through the call isn't interrupted > again. I think you're thinking of EINTR, not EAGAIN. regards, tom lane