Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 4C64A2E0041 for ; Tue, 26 Feb 2008 03:09:27 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 19330-01 for ; Tue, 26 Feb 2008 03:09:24 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id BD2D32E002F for ; Tue, 26 Feb 2008 03:09:24 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m1Q79Lbb026318; Tue, 26 Feb 2008 02:09:21 -0500 (EST) To: Darren Reed cc: Shoaib Mir , pgsql-admin@postgresql.org Subject: Re: How to reindex when unable to open relation? In-reply-to: <47C3B8EC.902@fastmail.net> References: <47C3AE1F.2010804@fastmail.net> <26104.1204008849@sss.pgh.pa.us> <47C3B8EC.902@fastmail.net> Comments: In-reply-to Darren Reed message dated "Mon, 25 Feb 2008 22:59:56 -0800" Date: Tue, 26 Feb 2008 02:09:21 -0500 Message-ID: <26317.1204009761@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/338 X-Sequence-Number: 28412 Darren Reed writes: > Tom Lane wrote: >> ... >> There's no info here to suggest exactly what went wrong; Darren, do you >> want to fess up to any hardware problems, tripped-over power cords, or >> such? What PG version is this anyway? > This is 8.2.6... and I'm starting to believe the hardware is just borked, > with all of the other troubles I've had. Well, there are no known data-loss bugs in 8.2.6, with of course the operative word being "known" ... > In an earlier bringup of the database, I received an error intended for > Linux kernels on a BSD box about a page not being zero... Yeah, I know exactly which message you mean; it was a defense against a bug that was present for a relatively short time in a few Linux kernel versions, and could only be exposed on multi-CPU hardware even so. If you're seeing that and other problems on a BSD kernel then I agree that hardware issues seem like a likely explanation. Have you tried running memtest86 and any other hardware diagnostics you can lay your hands on? regards, tom lane