Date: Tue, 15 Nov 2005 14:04:38 -0500 (EST)
From: Qingqing Zhou <zhouqq@cs.toronto.edu>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: icub3d@gmail.com, pgsql-admin@postgresql.org
Subject: Re: ERROR: could not read block
In-Reply-To: <4379B89302000025000006E6@gwmta.wicourts.gov>
Message-ID: <Pine.LNX.4.58.0511151356040.24384@eon.cs>
References: <4379B89302000025000006E6@gwmta.wicourts.gov>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


>
> 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