Re: ERROR: could not read block
От | Qingqing Zhou |
---|---|
Тема | Re: ERROR: could not read block |
Дата | |
Msg-id | Pine.LNX.4.58.0511161317440.13032@eon.cs обсуждение исходный текст |
Ответ на | Re: ERROR: could not read block ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>) |
Ответы |
Re: ERROR: could not read block
|
Список | pgsql-admin |
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
В списке pgsql-admin по дате отправления: