Re: Detecting corrupted pages earlier - Mailing list pgsql-hackers

From Andrew Sullivan
Subject Re: Detecting corrupted pages earlier
Date
Msg-id 20030403033311.GH17411@libertyrms.info
Whole thread Raw
In response to Re: Detecting corrupted pages earlier  (Jason Earl <jason.earl@simplot.com>)
Responses Re: Detecting corrupted pages earlier  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Apr 02, 2003 at 02:07:02PM -0700, Jason Earl wrote:

> There are some cases where this particular feature would be useful.
> What needs to be done is to make the feature less dangerous to the
> newbie without making it less useful to the person who actually needs
> the functionality.

I'll repeat what I said before (I think to Tom): "That's a pretty big
foot-gun you've got there."  I cannot possibly imagine what sort of
data-recovery situation would warrant running with the option turned
on all the time.  You know you have big-trouble, oh-no, ISP ran over
the tapes while they were busy pitching magnets through your cage,
data corruption problems, and this is your best hope for recovery? 
Great.  Log in, turn on this option, and start working.  But across
every back end?  It's the doomsday device for databases.  Emergency
recovery options are _good_: everyone has his favourite UNIX file
undeletion story.  But it's sure not a good idea to give everyone
root just in case she or he deletes some file.

A

-- 
----
Andrew Sullivan                         204-4141 Yonge Street
Liberty RMS                           Toronto, Ontario Canada
<andrew@libertyrms.info>                              M2P 2A8                                        +1 416 646 3304
x110



pgsql-hackers by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: contrib and licensing
Next
From: Tom Lane
Date:
Subject: Re: contrib and licensing