| From: | John R Pierce <pierce(at)hogranch(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: database corruption questions |
| Date: | 2012-10-13 22:54:12 |
| Message-ID: | 5079F114.2020504@hogranch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 10/13/12 3:04 PM, Leif Biberg Kristensen wrote:
> Lørdag 13. oktober 2012 23.53.03 skrev Heine Ferreira :
>> >Hi
>> >
>> >Are there any best practices for avoiding database
>> >corruption?
> In my experience, database corruption always comes down to flaky disk drives.
> Keep your disks new and shiny eg. less than 3 years, and go for some kind of
> redundancy in a RAID configuration.
also, ECC RAM so creeping bit rot doesn't slip in from memory without
detection. if you use a raid controller with a write-back cache, be
sure it has BBU or flash-back.
--
john r pierce N 37, W 122
santa cruz ca mid-left coast
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vibhor Kumar | 2012-10-13 23:31:37 | Re: citext question |
| Previous Message | David Johnston | 2012-10-13 22:34:45 | Re: citext question |