From: | Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | icub3d(at)gmail(dot)com, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: ERROR: could not read block |
Date: | 2005-11-15 19:04:38 |
Message-ID: | Pine.LNX.4.58.0511151356040.24384@eon.cs |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2005-11-15 19:14:37 | Re: ERROR: could not read block |
Previous Message | Scott Marlowe | 2005-11-15 18:28:46 | Re: Restore a PG database in Windows |