Re: ERROR: could not read block

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <zhouqq(at)cs(dot)toronto(dot)edu>
Cc: <icub3d(at)gmail(dot)com>,<pgsql-admin(at)postgresql(dot)org>, <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: ERROR: could not read block
Date: 2005-11-16 20:24:43
Message-ID: 437B412B020000250000079B@gwmta.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Our DBAs reviewed the Microsoft documentation you referenced,
modified the registry, and rebooted the OS. We've been beating
up on the database without seeing the error so far. We'll keep at
it for a while.

-Kevin

>>> Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu> >>>

On Wed, 16 Nov 2005, Kevin Grittner wrote:

> Ran with this change. Didn't take long to hit it.
>
> [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
> [2005-11-16 11:59:29.015 ] 4904 <dtr dtr 165.219.88.22(60649)> ERROR:
> could not read block 25447 of relation 1663/16385/1494810: Invalid
> argument
>

1450 ERROR_NO_SYSTEM_RESOURCES
Insufficient system resources exist to complete the requested service

SQL Server 7.0 experienced the same problem before:
http://support.microsoft.com/default.aspx?scid=kb;en-us;274310

Some registration value tweak to solve it (for backup service):
http://support.microsoft.com/default.aspx?scid=kb;en-us;304101

I have to go out for a while ... Kevin, can you take a look at the 2nd
thread to see if it is possible to change some reg values to temporarily
solve the problem. A more robust solution will follow a retry style
following thread 1 I guess.

Cheers,
Qingqing

Browse pgsql-admin by date

  From Date Subject
Next Message Bruno Wolff III 2005-11-16 20:43:15 Re: md5 collision generator
Previous Message Flávio Brito 2005-11-16 20:21:31 Receive a record not a tuple - plpgsql