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 2404AD1B97B for ; Mon, 1 Mar 2004 20:05:50 +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 68418-07 for ; Mon, 1 Mar 2004 16:05:48 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 9D93FD1B4E7 for ; Mon, 1 Mar 2004 16:05:46 -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 i21K5bbc008338; Mon, 1 Mar 2004 15:05:40 -0500 (EST) To: "Marc Mitchell" Cc: pgsql-admin@postgresql.org Subject: Re: Row data corruption under 7.3.5 In-reply-to: <004101c3ffbb$ebce29f0$7201050a@MarcM8500> References: <004101c3ffbb$ebce29f0$7201050a@MarcM8500> Comments: In-reply-to "Marc Mitchell" message dated "Mon, 01 Mar 2004 12:35:07 -0600" Date: Mon, 01 Mar 2004 15:05:37 -0500 Message-ID: <8337.1078171537@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/8 X-Sequence-Number: 12578 "Marc Mitchell" writes: > In each case, by examining the copy table output up to the point where > it errors out, a single row could be identified that contained corrupted > char/varchar values but could be queried using primary key or numeric > lookups. We've been able to work around the issue by deleting the row > and manually re-inserting it based on values determined from a previous > backup. Note that in each case, it has been determined that the corrupt > row existed without a problem earlier as it could be found in old > backups. Thus the rows seem to get into the table ok but got wacked at > some future point in time. > Any ideas on what's causing this? Hardware problems possibly? You might try running memtest86 or some such. It would be good to take note of the exact bit pattern of the corruption, if you can match up correct and corrupted versions of the rows. regards, tom lane