Skip site navigation (1) Skip section navigation (2)

Re: ERROR: could not read block

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, icub3d(at)gmail(dot)com, pgsql-admin(at)postgresql(dot)org
Subject: Re: ERROR: could not read block
Date: 2005-11-16 18:58:13
Message-ID: 9705.1132167493@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)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

In response to

pgsql-admin by date

Next:From: Bruno Wolff IIIDate: 2005-11-16 19:35:24
Subject: Re: Reg: Changing Column type
Previous:From: Qingqing ZhouDate: 2005-11-16 18:25:36
Subject: Re: ERROR: could not read block

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group