Re: ERROR: could not read block
От | Qingqing Zhou |
---|---|
Тема | Re: ERROR: could not read block |
Дата | |
Msg-id | Pine.LNX.4.58.0511151356040.24384@eon.cs обсуждение исходный текст |
Ответ на | Re: ERROR: could not read block ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>) |
Список | pgsql-admin |
> > I reran the query. Same error, same relation, different block. > > dtr=> UPDATE > dtr-> "DbTranRepository" > dtr-> SET "userId" = UPPER("userId") > dtr-> WHERE ( > dtr(> ("userId" <> UPPER("userId")) AND > dtr(> ("timestampValue" BETWEEN '2005-10-28' AND '2005-11-15')); > ERROR: could not read block 1118215 of relation 1663/16385/16483: > Invalid argument > So this is a big query? Somebody reported this error when IO is intensive. To conclude the reports we have received: (1) If IO is intensive (no matter you have anti-virus software or not), you may encounter "invalud argument" error; (2) In some cases, anti-virus software could cause "invalid argument" error; (3) You may encounter "permission denied" problem (no matter you have anti-virus software or not) in some unknown condition; Unfortunately we haven't found out the cause of this problem ... I am thinking an urgent need is let PG print the GetLastError() for Windows version as well. Regards, Qingqing
В списке pgsql-admin по дате отправления: