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.
>>> 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 184.108.40.206(60649)> LOG:
> read failed on relation 1663/16385/1494810: -1 bytes, 1450
> [2005-11-16 11:59:29.015 ] 4904 <dtr dtr 220.127.116.11(60649)> ERROR:
> could not read block 25447 of relation 1663/16385/1494810: Invalid
Insufficient system resources exist to complete the requested service
SQL Server 7.0 experienced the same problem before:
Some registration value tweak to solve it (for backup service):
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.
pgsql-admin by date
|Next:||From: Bruno Wolff III||Date: 2005-11-16 20:43:15|
|Subject: Re: md5 collision generator|
|Previous:||From: Flávio Brito||Date: 2005-11-16 20:21:31|
|Subject: Receive a record not a tuple - plpgsql|