Re: bad block problem

From: Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>
To: Walter Hurry <walterhurry(at)lavabit(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: bad block problem
Date: 2011-12-08 01:02:15
Message-ID: 4EE00C97.3080905@ringerc.id.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On 12/08/2011 08:20 AM, Walter Hurry wrote:
> On Wed, 07 Dec 2011 22:20:30 +0000, jkells wrote:
>
>> I am relying on identifying and correcting a bad block.
>
> Well, good luck with that. Most of the time you can't. Just check your
> disk, replace it if necessary, restore from your backup and roll forward.
>
> Oh, you can't do that, since you didn't bother to back up. Never mind.

Unless you're using synchronous replication to clone *every* transaction
on commit to a spare machine, you'll still lose transactions on a
failure no matter how good your backups are.

Even if the OP was doing nightly dumps, they'd be entirely justified in
wanting to try to get a more recent dump on failure.

If they're not backing up at all, yes, that was dumb, but they know that
now. Asking for help isn't unreasonable, and this isn't a stupid "just
google it" question. They've made an effort, posted useful info and log
output, etc. Please don't be too hard on them.

--
Craig Ringer

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Craig Ringer 2011-12-08 01:05:53 Re: bad block problem
Previous Message Walter Hurry 2011-12-08 00:20:40 Re: bad block problem