X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id D76E1D1DC9E for ; Wed, 17 Mar 2004 16:53:49 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 84661-04 for ; Wed, 17 Mar 2004 12:53:40 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id AD078D1D2DB for ; Wed, 17 Mar 2004 12:53:38 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i2HGrb2B025826; Wed, 17 Mar 2004 11:53:37 -0500 (EST) To: "Marc Mitchell" Cc: pgsql-admin@postgresql.org Subject: Re: Row data corruption under 7.3.5 In-reply-to: <001f01c40c3a$b1a95e80$6701050a@MarcM8500> References: <001f01c40c3a$b1a95e80$6701050a@MarcM8500> Comments: In-reply-to "Marc Mitchell" message dated "Wed, 17 Mar 2004 10:12:47 -0600" Date: Wed, 17 Mar 2004 11:53:36 -0500 Message-ID: <25825.1079542416@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/236 X-Sequence-Number: 12805 "Marc Mitchell" writes: > This is follow-up to a problem first reported on 3/1/04. The problem > has continued to occur intermittently and recently we experienced the > first occurrence where the first column of a table was the column where > the corrupted and thus we could not recover it. It would be useful to look at pg_filedump output for the affected pages. See http://sources.redhat.com/rhdb/utilities.html to get that program. I find "-i -f" options to be its most useful display format, although the raw hex dump (-d) is also good to look at when investigating data corruption. The first part of the TID (15 in your latest example) is the block number within the table file; you can use contrib/oid2name if you need help figuring out which file is the table you want. > We've observed nothing that would lead us to believe there are any > hardware problems. Have you done anything to proactively test for hardware problems? memtest86, badblocks, etc? It's possible you have a software problem, but the symptoms sound more like hardware glitches to me. regards, tom lane