Re: Do we need more emphasis on backup? - Mailing list pgsql-general

From jseymour@linxnet.com (Jim Seymour)
Subject Re: Do we need more emphasis on backup?
Date
Msg-id 20040623112837.6C8F7430E@jimsun.linxnet.com
Whole thread Raw
In response to Re: Do we need more emphasis on backup?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Do we need more emphasis on backup?  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-general
Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
[snip]
>
> We do need to point out that you're only as reliable as your last
> backup.  I'm not sure exactly where to say this.
[snip]
>

Hmph.  Backups are for mitigation against a catastrophic failure
destroying or corrupting main storage.  And even then: Subtle errors
can induce data corruption that may go un-noticed until it's too late.
(I.e.:  The last correct backups have been over-written, retired, so
old they've become unreadable, so old the data's no longer useful,
etc.)

My position is that your data is only as reliable as your hardware,
period.  Use cheap (usually PC, sorry) hardware and, well...  I wonder
how many people are aware of the fact that the cheaper PCs don't even
have parity memory anymore?  Then there are the issues with IDE
drives.  (Don't recall those, exactly - don't use 'em.)

One of the other mailing lists I'm on: The project developer, whenever
somebody comes on list and says "Your code is blowing up, losing stuff,
corrupting stuff," or whatever, first asks "What hardware are you
running?"  IIRC, he gives short shrift to complainants running
inexpensive PC hardware.  He won't spend any time on the complaint
until they prove it's *not* their hardware.

Jim

pgsql-general by date:

Previous
From: Christian Kratzer
Date:
Subject: Logging duration of batch runs
Next
From: Martijn van Oosterhout
Date:
Subject: Re: Logging duration of batch runs