pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Robert (DEQ) Burgholzer <Robert.Burgholzer@deq.virginia.gov>
To: pgsql-admin@postgresql.org
Subject: Re: catalog corruption causes
Date: Fri, 06 Aug 2010 13:57:34 -0500
Message-ID: <4C5C14CE02000025000342D6@gw.wicourts.gov> (raw)
In-Reply-To: <B6C40D17104BEF47B1CB85623CDFAC63AB4AED@COVMSGCES-EMB13.cov.virginia.gov>
References: <B6C40D17104BEF47B1CB85623CDFAC63AB4AED@COVMSGCES-EMB13.cov.virginia.gov>

"Burgholzer, Robert (DEQ)" <Robert.Burgholzer@deq.virginia.gov>
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



view thread (6+ messages)  latest in thread

Message-ID: <4C5C14CE02000025000342D6@gw.wicourts.gov>
Permalink:  ../4C5C14CE02000025000342D6@gw.wicourts.gov/
Also on:    postgresql.org/message-id/4C5C14CE02000025000342D6@gw.wicourts.gov

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: Kevin.Grittner@wicourts.gov, Robert.Burgholzer@deq.virginia.gov
  Subject: Re: catalog corruption causes
  In-Reply-To: <4C5C14CE02000025000342D6@gw.wicourts.gov>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox