X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id 988C7D6D16
	for <pgsql-admin-postgresql.org@localhost.postgresql.org>;
	Wed, 16 Nov 2005 14:58:17 -0400 (AST)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 48763-09
	for <pgsql-admin-postgresql.org@localhost.postgresql.org>;
	Wed, 16 Nov 2005 18:58:17 +0000 (GMT)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by svr1.postgresql.org (Postfix) with ESMTP id C2DF1DB932
	for <pgsql-admin@postgresql.org>; Wed, 16 Nov 2005 14:58:14 -0400 (AST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id jAGIwDkI009706;
	Wed, 16 Nov 2005 13:58:13 -0500 (EST)
To: Qingqing Zhou <zhouqq@cs.toronto.edu>
cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>, icub3d@gmail.com,
	pgsql-admin@postgresql.org
Subject: Re: ERROR: could not read block 
In-reply-to: <Pine.LNX.4.58.0511161317440.13032@eon.cs> 
References: <437B21E90200002500000781@gwmta.wicourts.gov>
	<Pine.LNX.4.58.0511161317440.13032@eon.cs>
Comments: In-reply-to Qingqing Zhou <zhouqq@cs.toronto.edu>
	message dated "Wed, 16 Nov 2005 13:25:36 -0500"
Date: Wed, 16 Nov 2005 13:58:13 -0500
Message-ID: <9705.1132167493@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0 required=5 tests=[AWL=0.000]
X-Spam-Score: 0
X-Spam-Level: 
X-Archive-Number: 200511/215
X-Sequence-Number: 19588

Qingqing Zhou <zhouqq@cs.toronto.edu> writes:
> On Wed, 16 Nov 2005, Kevin Grittner wrote:
>> [2005-11-16 11:59:29.015 ] 4904 <dtr dtr 165.219.88.22(60649)> LOG:
>> read failed on relation 1663/16385/1494810: -1 bytes, 1450

> 1450 ERROR_NO_SYSTEM_RESOURCES
> Insufficient system resources exist to complete the requested service

Hmm ... seems like win32/error.c ought to be mapping that to something
more helpful than EINVAL.  The link you mention suggests that we ought
to retry the read, so maybe mapping it to EINTR would be the most useful
thing.  I seem to recall that we've heard about read() sometimes failing
with EINTR on Unix-with-NFS configurations ...

			regards, tom lane