Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 9A5799FA02C for ; Mon, 18 Dec 2006 15:56:30 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 03641-09 for ; Mon, 18 Dec 2006 15:55:52 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id D637A9FA252 for ; Mon, 18 Dec 2006 15:55:51 -0400 (AST) 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 kBIJtnKt027861; Mon, 18 Dec 2006 14:55:49 -0500 (EST) To: "Edoardo Ceccarelli" cc: pgsql-admin@postgresql.org Subject: Re: pg_clog In-reply-to: <2c5b22d10612181101r3c0ca187qac319f41587cec2a@mail.gmail.com> References: <2c5b22d10612180957s78fa6fd8s9f913673bfadbe0e@mail.gmail.com> <25199.1166467713@sss.pgh.pa.us> <2c5b22d10612181101r3c0ca187qac319f41587cec2a@mail.gmail.com> Comments: In-reply-to "Edoardo Ceccarelli" message dated "Mon, 18 Dec 2006 20:01:17 +0100" Date: Mon, 18 Dec 2006 14:55:49 -0500 Message-ID: <27860.1166471749@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/256 X-Sequence-Number: 24048 "Edoardo Ceccarelli" writes: > I bet a crashing process could cause that data corruption, right? No, Postgres is remarkably resistant to causing corruption during a crash; it's deliberately engineered that way. I don't say this *couldn't* be the explanation but it shouldn't be your first guess. Frankly I think hardware flakiness is more likely. There are currently two known crashing bugs in 8.2.0, and both of them will result in a simple crash, no data corruption. regards, tom lane