pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <scott.marlowe@gmail.com>
To: Achilleas Mantzios <achill@matrix.gatewaynet.com>
Cc: pgsql-admin@postgresql.org, Michael Monnerie <michael.monnerie@is.it-management.at>
Subject: Re: 8.3.5 broken after power fail
Date: Tue, 17 Feb 2009 02:34:50 -0700
Message-ID: <dcc563d10902170134p53d4a994s1f769bcb526e49e5@mail.gmail.com> (raw)
In-Reply-To: <200902171112.31632.achill@matrix.gatewaynet.com>
References: <200902170954.52983@zmi.at>
	<200902171112.31632.achill@matrix.gatewaynet.com>

2009/2/17 Achilleas Mantzios <achill@matrix.gatewaynet.com>:
> Óôéò Tuesday 17 February 2009 10:54:52 ï/ç Michael Monnerie Ýãñáøå:
>
>> * your daughter with 3.5 years switching off the power supply of the
>> server
> 1st line of defense is to set your system to shutdown normally when the power button is pressed.
> 2nd line of defense is to get your self a decent UPS unit
>
> My daughter does this all the time on our family FreeBSD box. No probs.
>
> Also at work at more than 20 tanker vessels running 7.4.2, the captains do that on a constant
> basis and PgSQL always has survived (more than the rest of the system anyways..)

Those are all good to have.  But no UPS is a replacement for hard
drives / RAID controllers / file systems that don't lie about fsync.

Nothing makes your database shine like being the only one in the
hosting center that survives sudden catastrophic power failure.

>> What can I do?

tether your daughter to the other side of the room?  I'm not sure
which parts of those mount options are dangerous or not.  I use ext3
stock with noatime.  And a battery backed RAID.  Smaller slower work
group / station controllers (i.e. 5 year old server conrollers) go for
pretty cheap and give pretty good performance with 2 or 4 drives.

AS for fixing it, I believe the answer involves creating a clog file
full of zeros 16Meg or so, and pg_reset_xlog.  Don't count on all your
data being there or all your FK-PK type relationships to be correct,
Immediately dump it, initdb and reload your data, fixing it as you go.



view thread (19+ messages)  latest in thread

Message-ID: <dcc563d10902170134p53d4a994s1f769bcb526e49e5@mail.gmail.com>
Permalink:  ../dcc563d10902170134p53d4a994s1f769bcb526e49e5@mail.gmail.com/
Also on:    postgresql.org/message-id/dcc563d10902170134p53d4a994s1f769bcb526e49e5@mail.gmail.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: scott.marlowe@gmail.com, achill@matrix.gatewaynet.com, michael.monnerie@is.it-management.at
  Subject: Re: 8.3.5 broken after power fail
  In-Reply-To: <dcc563d10902170134p53d4a994s1f769bcb526e49e5@mail.gmail.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