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 1BA32D940E for ; Tue, 15 Nov 2005 20:07:34 -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 35466-02 for ; Wed, 16 Nov 2005 00:07:35 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from cliff.cs.toronto.edu (cliff.cs.toronto.edu [128.100.3.120]) by svr1.postgresql.org (Postfix) with ESMTP id 83A73D7C5C for ; Tue, 15 Nov 2005 20:07:31 -0400 (AST) Received: from eon.cs (eon.cs.toronto.edu [128.100.3.15]) by cliff.cs.toronto.edu (Postfix) with ESMTP id 241395FD03; Tue, 15 Nov 2005 19:07:34 -0500 (EST) Received: by eon.cs (Postfix, from userid 1300) id 2268B7F4; Tue, 15 Nov 2005 19:07:34 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by eon.cs (Postfix) with ESMTP id 14825544; Tue, 15 Nov 2005 19:07:34 -0500 (EST) Date: Tue, 15 Nov 2005 19:07:34 -0500 (EST) From: Qingqing Zhou X-X-Sender: zhouqq@eon.cs To: Kevin Grittner Cc: icub3d@gmail.com, mha@sollentuna.net, pgsql-admin@postgresql.org Subject: Re: ERROR: could not read block In-Reply-To: <4379FE9B020000250000072F@gwmta.wicourts.gov> Message-ID: References: <4379FE9B020000250000072F@gwmta.wicourts.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.359 required=5 tests=[AWL=-0.120, DNS_FROM_RFC_ABUSE=0.479] X-Spam-Score: 0.359 X-Spam-Level: X-Archive-Number: 200511/201 X-Sequence-Number: 19574 On Tue, 15 Nov 2005, Kevin Grittner wrote: > I got the error log working on Windows (with redirect_stderr). I had > to stop and restart postgres to do so. I ran the query (for the fourth > time), and it completed successfully. Strange - the phyiscal read for the 2nd, 3rd, 4th time should be the same, if we intent to think of the IO presure. > > Is there anything that anyone wants me to do at this point, to try > to pin down a cause, or do I drop it here? > Since you can reproduce the error with big chance, I think it is a good chance to pin down a cause now. It would be useful to know the GetLastError() instead of a tranlated errno. Can you patch the code like this (patch smgrread()): http://archives.postgresql.org/pgsql-bugs/2005-10/msg00050.php Regards, Qingqing