Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 88B649F9EF3 for ; Fri, 13 Oct 2006 11:30:48 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 54912-05 for ; Fri, 13 Oct 2006 14:30:12 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 842269FB272 for ; Fri, 13 Oct 2006 11:30:11 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k9DEU7w9029603; Fri, 13 Oct 2006 10:30:07 -0400 (EDT) To: Enrico cc: pgsql-admin@postgresql.org Subject: Re: Disaster recovery: pg_class In-reply-to: <20061013112929.1cbb7b9e@mypc.ricordatasystem.info> References: <20061013112929.1cbb7b9e@mypc.ricordatasystem.info> Comments: In-reply-to Enrico message dated "Fri, 13 Oct 2006 11:29:29 +0200" Date: Fri, 13 Oct 2006 10:30:07 -0400 Message-ID: <29602.1160749807@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200610/91 X-Sequence-Number: 23394 Enrico writes: > After a system crash, I have this error: > SELECT * from mytable; > WARNING: could not write block 14 of 1663/1743558/1259 > DETAIL: Multiple failures --- write error may be permanent. > ERROR: xlog flush request 4/D43E0A00 is not satisfied --- flushed only to 4/D42700F0 > CONTEXT: writing block 14 of relation 1663/1743558/1 I'm not convinced there's anything much there you need to fix. You should look into why the filesystem seems to have lost part of your WAL file --- that strongly suggests that the disk or kernel is lying about write ordering, which will cause you problems eventually. But this message per se will go away as soon as the WAL endpoint moves another 1.5Mb. Unless there's other corruption elsewhere you'll be fine. regards, tom lane