pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Naomi Walker <nwalker@eldocomp.com>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: pgsql-admin@postgresql.org
Subject: Re: 8.3.5 broken after power fail SOLVED
Date: Sat, 21 Feb 2009 07:34:53 -0700
Message-ID: <49A0110D.8020302@eldocomp.com> (raw)
In-Reply-To: <dcc563d10902210140x22e9b4bckcf17ac02e4c91769@mail.gmail.com>
References: <43a3a0bccd3684972f33e0051b45f2b4@webmail.zmi.at>
	<200902210943.27875@zmi.at>
	<dcc563d10902210140x22e9b4bckcf17ac02e4c91769@mail.gmail.com>

Other than disaster tests, how would I know if I have an system that 
lies about fsync?


>
> We preach this again and again.  PostgreSQL can only survive a power
> outage type failure ONLY if the hardware / OS / filesystem don't lie
> about fsync.  If they do, all bets are off, and this kind of failure
> means you should really failover to another machine or restore a
> backup.
>
> It's why you have to do possibly destructive tests to see if your
> server stands at least some chance of surviving this kind of failure,
> log shipping for recovery, and / or replication of another form (slony
> etc...) to have a reliable server.
>
> The recommendations for recovery of data are just that, recovery
> oriented.  They can't fix a broken database at that point.  You need
> to take it offline after this kind of failure if you can't trust your
> hardware.
>
> Usually when it finds something wrong it just won't start up.
>
>   


-- 
------------------------------------------------------------------------
Naomi Walker                          Chief Information Officer
Eldorado Computing, Inc               nwalker@eldocomp.com
  ---An EDS Company                   602-604-3100
------------------------------------------------------------------------
Hard things are put in our way, not to stop us, but to call out our
courage and strength. -- Anonymous
------------------------------------------------------------------------




view thread (6+ messages)  latest in thread

Message-ID: <49A0110D.8020302@eldocomp.com>
Permalink:  ../49A0110D.8020302@eldocomp.com/
Also on:    postgresql.org/message-id/49A0110D.8020302@eldocomp.com

 · 

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: nwalker@eldocomp.com, scott.marlowe@gmail.com, michael.monnerie@is.it-management.at
  Subject: Re: 8.3.5 broken after power fail SOLVED
  In-Reply-To: <49A0110D.8020302@eldocomp.com>

* 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