Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 9AF44632D24 for ; Fri, 6 Aug 2010 15:57:45 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 71141-04 for ; Fri, 6 Aug 2010 18:57:37 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from gw.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by mail.postgresql.org (Postfix) with ESMTP id 9DF8E632BBB for ; Fri, 6 Aug 2010 15:57:37 -0300 (ADT) Received: from Courts-MTA by gw.wicourts.gov with Novell_GroupWise; Fri, 06 Aug 2010 13:57:35 -0500 Message-Id: <4C5C14CE02000025000342D6@gw.wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 8.0.1 Date: Fri, 06 Aug 2010 13:57:34 -0500 From: "Kevin Grittner" To: "Robert (DEQ) Burgholzer" , Subject: Re: catalog corruption causes References: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.311 tagged_above=-10 required=5 tests=BAYES_20=-0.001, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201008/47 X-Sequence-Number: 35296 "Burgholzer, Robert (DEQ)" wrote: > I am trying to get my head around what causes catalog corruption. From what I've seen many are caused by things outside of PostgreSQL -- like bad disk, bad drivers, OS bugs, running on network drives which aren't reliable, write caches without battery back-up, anti-virus software, etc. Another common cause is using faster-but-unreliable PostgreSQL configuration settings like fsync=off or full_page_writes=off. If that's couple with a kill -9 or a crash of hardware or OS, you can get corruption. Then there's the possibility of PostgreSQL bugs. Make sure you use a recent minor release of whatever major release you're on, so you get the benefit of bug fixes. And I recommend staying away from VACUUM FULL -- among the many other reasons there are to avoid it, it seems to have more than it's share of odd corner cases where things can go wrong. Less likely, but still possible, is that there's some malicious element involved. Keep your security tight to minimize the risk of that. -Kevin