X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 7F1D9DB6D0 for ; Tue, 15 Nov 2005 15:14:55 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 76401-10 for ; Tue, 15 Nov 2005 19:14:54 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from gwmta.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by svr1.postgresql.org (Postfix) with ESMTP id 77255D71C1 for ; Tue, 15 Nov 2005 15:14:52 -0400 (AST) Received: from Courts-MTA by gwmta.wicourts.gov with Novell_GroupWise; Tue, 15 Nov 2005 13:14:52 -0600 Message-Id: <4379DF3D0200002500000714@gwmta.wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 7.0 Date: Tue, 15 Nov 2005 13:14:37 -0600 From: "Kevin Grittner" To: Cc: , Subject: Re: ERROR: could not read block Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[none] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200511/196 X-Sequence-Number: 19569 The table has about 23.3 million rows, of which about 200,000 will be affected by this update. Run time is about an hour. During the first run, the table was the target of about 45,000 inserts. This rerun was done as the only task. A third run (also by itself) gave this: ERROR: could not read block 1482762 of relation 1663/16385/16483: Invalid argument So the block number is increasing each time. I'm inclined to think that this is the result of the scan passing over rows added by itself. -Kevin >>> Qingqing Zhou >>> > 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