| From: | John R Pierce <pierce(at)hogranch(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: FW: getting error while running sql on mm_activealrm table |
| Date: | 2014-12-04 06:14:25 |
| Message-ID: | 547FFBC1.10400@hogranch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 12/3/2014 9:30 PM, M Tarkeshwar Rao wrote:
> I have found corrupted indexes are usually a sign that something is not well with the server. It is good to check and make sure memory, CPU's and hard drives are all happy and not reporting problems. I have found overheating servers to be particularly prone to index corruption and if indexes can get corrupt one has to worry about data becoming corrupt too.
do your servers not have ECC memory? the number one source of data
corruption is cached data getting transient one-bit errors, which occur
at a more common rate than you might expect if you have many gigabytes
of ram... ECC will fix and report these single bit errors.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sameer Kumar | 2014-12-04 06:28:35 | Re: High Availability Cluster |
| Previous Message | M Tarkeshwar Rao | 2014-12-04 05:30:20 | Re: FW: getting error while running sql on mm_activealrm table |